More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Secret Scan

    1

    Find leaked API keys, tokens and passwords in files, commits, history or pasted text, and stop your coding agent from writing or committing them.

    Free

    1 useSecurity scanned
    Secret Scan

    Secret Scan

    Example session with this skill installed

    I'm about to make this repo public. Check it for leaked keys first, including old commits.

    • Read your context and instructions
    • Compiled the secret scan

    Not ready to go public yet: 3 secrets found

    $ secret_scan.py --history
    CRITICAL Anthropic API key
             src/llm.py:2 @ 777f163563f4 (Dev)
             sk-a************************rS   fingerprint d0b5e145ef40a366
             rotate: Claude Console, API keys: delete the key and create a new one.
    HIGH     Slack webhook URL
             src/notify.py:1 @ 19b35b09f5ed (Dev)
             http************************S7   fingerprint d560ac29ab5a8a8b
    MEDIUM   Secret-looking config value
             config/settings.yml:3 @ 19b35b09f5ed (Dev)
    
    3 finding(s) (git history): 1 critical, 1 high, 1 medium
    

    The Anthropic key is no longer in the code, but it

    is still in commit 777f163. Anyone who clones the public repo gets it.

    Do this, in this order

    Rotate the Anthropic key in the Claude Console and the Slack webhook in your Slack app settings. Removing them from git does not make them safe.
    2.

    Move the values to the environment: I replaced them with os.environ["ANTHROPIC_API_KEY"], os.environ["SLACK_WEBHOOK_URL"] and ${DB_PASSWORD}, added the names to .env.example, and confirmed .env is git-ignored.
    3.

    Rewrite history before publishing, since the repo is going public: git filter-repo --replace-text on a mirror clone (exact commands are in references/remediation.md), then push the mirror.
    4. Re-scan: secret_scan.py --history must come back clean.
    5. Guard: secret_scan.py install-hook blocks this at commit time from now on.

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

    About this skill

    What it does

    One Python file that finds API keys, tokens, private keys and passwords before they reach a commit, a pushed branch, a chat message or a published package. Standard library only, no network: your code and secrets never leave the machine.

    secret_scan.py                    # working tree
    secret_scan.py --staged           # before a commit
    secret_scan.py --diff origin/main # a branch or PR
    secret_scan.py --history          # every commit, every branch
    secret_scan.py package.zip        # a package before publishing
    secret_scan.py --stdin            # text before you paste it
    

    Rules that fit real projects

    • 39 provider-specific rules: Anthropic, OpenAI, AWS, GitHub, GitLab, Stripe, Slack, Google, Groq, Supabase, Databricks, Telegram, Discord, Twilio, SendGrid, npm, PyPI, Hugging Face, Shopify, DigitalOcean, Azure and more
    • Tuned heuristics for passwords, connection strings, config values, bearer tokens and committed .env files
    • Low noise: placeholders, ${VAR}, os.environ[...], lockfiles and fixtures handled. Zero failing findings on two real open-source repositories of about 3,000 files
    • Output is always redacted, with where to rotate each key. JSON and SARIF for GitHub code scanning. Baseline for existing repos

    Guard rails

    • A git pre-commit hook that keeps your existing hook
    • A Claude Code hook that blocks the agent from writing a key into a tracked file, or committing or pushing one (including git add -A && git commit, git -C, and first pushes), tells it to use an environment variable instead, and cannot be waved through by the agent itself

    Includes a remediation playbook (rotate first, then fix, then decide about history) and CI recipes. 102 automated tests; the fake tokens in them are assembled at runtime, so the package itself scans clean.

    Built by Nex AI, nex-ai.be

    Pattern and entropy based: it finds the formats it knows and secret-looking assignments, and does not call providers to check whether a key is live. Skips binaries, files over 2 MB, lockfiles and source maps. History scans cover commits reachable from refs, not stashes or the reflog.

    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 any payment.

    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

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 29 days ago

    • Free with an Agensi account

    Requires

    Python 3.8+
    git (for staged, diff and history scans)
    Python
    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Terminal to run secret_scan.py and git (staged, diff and history scans). Read files to scan them. Write files only when the user asks for a hook: install-hook writes .git/hooks/pre-commit plus a copy of the script, install-claude-hook writes .claude/settings.local.json after a backup. No network: nothing is sent anywhere.

    Listed29 days ago

    What's inside

    Frequently Asked Questions

    No. That would mean sending your keys to the provider. Treat high and critical findings as live and rotate them.

    They are excellent in CI. This needs nothing installed beyond Python, runs anywhere an agent runs, and comes with the agent hook and the remediation playbook.

    Add secret-scan: allow on the line, add the fingerprint to .secretscanignore, or create a baseline for an existing repo. In the Claude Code hook, only you can allow high and critical findings.

    New in Security