Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Secret Leak Scanner

    1

    Scans your codebase or staged git changes for accidentally committed API keys, AWS credentials, private keys and tokens before you push.

    $5

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    Security scanned
    Secret Leak Scanner

    Secret Leak Scanner

    Example session with this skill installed

    Check my staged changes for any secrets before I commit.

    • Read your context and instructions
    • Compiled the secret leak scanner
    [HIGH] config.py:1  AWS Access Key ID  ->  AKIA************MNOP
[HIGH] config.py:2  AWS Secret Access Key  ->  aws_**********************************************************KEY
[MEDIUM] config.py:2  Env-style Secret Assignment  ->  aws_**********************************************************KEY
[HIGH] config.py:3  Stripe Secret Key  ->  sk_l*****************************STUV
[HIGH] config.py:4  DB Connection String w/ password  ->  post**********************************************prod

    Scan complete. 5 potential finding(s).
    Review each finding — HIGH severity items should be treated as real leaks until proven otherwise.

    Summary: Found 4 high-confidence leaks (AWS key pair, Stripe live key, DB connection string with embedded password) and 1 medium-confidence finding. Recommend rotating the AWS and Stripe keys immediately since they were staged for commit, moving all four values to environment variables, and adding config.py to .gitignore before committing again.

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

    What you get

    Pre-commit code reviewsAuditing a repo before making it publicCI/CD pipeline security checksOnboarding — checking a cloned repo for old leaked keysReviewing pull requests for accidental credential exposureCleaning up before open-sourcing a private project

    About this skill

    Catches leaked secrets before they hit your git history — AWS access keys, GitHub/GitLab/Slack/Stripe/Twilio tokens, private key blocks, JWTs, and database connection strings with embedded passwords. Runs entirely offline with zero dependencies (pure Python stdlib), so no data ever leaves your machine. Three modes: scan a full directory, check only your staged changes right before a commit, or sweep your entire git history for secrets that were leaked in the past. Every finding is redacted in the output — you get the file, line number, and pattern type, never the full secret in plaintext. Built for developers who want a fast pre-commit safety net without setting up a full enterprise secret-scanning pipeline. High-confidence detectors (AWS keys, private keys, provider tokens) are flagged separately from medium-confidence heuristics (generic key assignments, high-entropy strings) so you're not drowning in false positives.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 1 month ago

    • Passed all security checks, Safe to install

    Listed1 month ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions