More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Hardcoded Secrets Check

    1

    Find API keys, tokens, private keys and database passwords in a project before you commit, publish or zip it: 18 providers by their real key formats, plus whether .gitignore keeps each file with a secret out of git.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Hardcoded Secrets Check

    Hardcoded Secrets Check

    Example session with this skill installed

    Check this project with hardcoded-secrets-check.

    • Read your context and instructions
    • Compiled the hardcoded secrets check

    $ python3 scripts/check_secrets.py examples/risky
    BLOCK .env.production:2 H04 PAYMENT_OR_MESSAGING_TOKEN
    Stripe live secret key: STRIPE_SECRET_KEY=<redacted>
    Why: A live payment or messaging credential is written in the file: a Stripe live secret or restricted key (sk_live_, rk_live_) or webhook secret (whsec_; Stripe says only pk_ keys are safe to expose), a Slack token (xoxb-, xoxp-, xapp-, xoxe.) or webhook URL, a Discord bot token or webhook URL, a Telegram bot token (bot ID, a colon, then 35 characters starting AA), a Twilio Auth Token (32 characters next to an AC Account SID) or a SendGrid key (SG., 69 characters). Someone can charge cards, issue refunds, read customer data, forge webhooks or message as you.
    Safer: Roll the key in the provider's dashboard now (Stripe API keys, Slack app settings, Discord Developer Portal, BotFather /revoke, Twilio Console, SendGrid API Keys) and load the new one from the environment or a secret manager on the server.

    BLOCK .env.production:3 H06 PASSWORD_IN_CONNECTION_STRING
    BLOCK .npmrc:2 H02 CODE_OR_PACKAGE_TOKEN
    BLOCK backend/settings.py:11 H01 CLOUD_ACCESS_KEY
    BLOCK deploy/deploy_key.pem:1 H05 PRIVATE_KEY
    BLOCK ml/train.py:4 H03 AI_API_KEY
    REVIEW .env.production H14 SECRETS_FILE_NOT_IGNORED
    REVIEW .npmrc H14 SECRETS_FILE_NOT_IGNORED
    REVIEW backend/settings.py:8 H12 SECRET_NAMED_LITERAL
    REVIEW backend/settings.py:14 H13 JWT_IN_FILE
    REVIEW deploy/deploy_key.pem H14 SECRETS_FILE_NOT_IGNORED
    REVIEW server/billing.js:2 H11 TEST_MODE_KEY
    REVIEW web/src/firebase.js:4 H15 CLIENT_KEY_NEEDS_RESTRICTION

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 9 files, 9 with text content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    STRIPE_SECRET_KEY=sk_live_... in a .env.production that .gitignore does not cover goes into the repository with the next git add ., and a Hugging Face or OpenAI key pasted into a training script ends up in every fork and backup. This skill finds those and the other ways secrets get written into files, and tells you how to fix each one.

    Your agent runs a scanner on every text file in the project (code, .env files, YAML, JSON, notebooks, docs and key files). It matches each provider's published format (prefix, length and characters), checks that a -----BEGIN PRIVATE KEY----- line is followed by real key data, reads database URLs and connection strings, and looks at settings whose names say they hold a secret. It skips plain placeholders (your_key_here, xxxx, ${VAR}, the AWS documentation key), lines marked fake in test files, and heuristic rules in docs, lock files and minified bundles, and it honors gitleaks:allow and pragma: allowlist secret. It then reads your .gitignore files: secrets in files git ignores stay out of the verdict and are counted in one closing line, and a secrets file git would commit is reported. It never calls a provider and never prints a secret. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach.

    What it checks

    BLOCK

    • H01: AWS access keys and secret keys (also in access-key CSVs and aws configure), Google API keys in server code (Gemini), Google OAuth client secrets, Azure Storage account keys, Supabase secret and service_role keys
    • H02: GitHub, GitLab, npm (including .npmrc _authToken) and PyPI tokens
    • H03: OpenAI, Anthropic, OpenRouter and Hugging Face keys
    • H04: Stripe live keys and webhook secrets, Slack, Discord and Telegram bot tokens and webhooks, Twilio Auth Tokens, SendGrid keys
    • H05: private keys (PEM, OpenSSH, PGP, PuTTY, age) that contain key data
    • H06: passwords in database URLs and connection strings to remote hosts

    REVIEW

    • H11: Stripe test keys and TestPyPI tokens
    • H12: secret-named settings with random-looking values (including Laravel APP_KEY and similar *_KEY values), literal Authorization headers, passwords for container hosts
    • H13: JWTs (Supabase anon keys and the jwt.io sample are skipped)
    • H14: .env, .npmrc, *.pem and similar files with a secret that no .gitignore rule covers
    • H15: Google API keys in Firebase, Android, iOS or Maps client configs that need API and app restrictions

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason, the key formats and the safer approach for each rule
    • A risky and a safe example project (Django, Express, Firebase, npm and deploy files), and the real report the scanner produces on the risky one

    Limits It reads the files as they are now: git history, other branches and CI logs are not searched, and it cannot tell whether a key still works. Ignore status comes from .gitignore files only, and files with more than 50 hits for one rule list the first 50. Binary key stores (.p12, .jks), short or word-like passwords, secrets split across lines and providers not listed above are not reported. NOT FLAGGED is not a guarantee.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    Static check of current file text. Git history, keys already revoked or still active, and files ignored through .git/info/exclude or a global excludes file are not checked. NOT FLAGGED is not a guarantee.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert keys (every one contains NOTREAL) written in real provider formats so the scanner can show each rule. None of them works, and nothing is contacted.

    Listed5 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. Values are masked in the report. Only the file, line, rule and a hidden preview are shown.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    The scanner, a rules guide with the reason and safer approach for every rule, a risky and a safe example project, and the real report the scanner prints on the risky example.

    New in Security