secrets pattern scanner

    1

    Scan files for API keys, tokens and private keys offline (gitleaks-style). AWS, GitHub/GitLab PATs, Slack, Stripe, Google, npm/PyPI, JWTs and PEM keys — values redacted.

    $8

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    secrets pattern scanner

    Example session with this skill installed

    Scan the current directory for any committed API keys or Slack tokens and give me a Markdown report.

    • Read your context and instructions
    • Compiled the secrets pattern scanner

    I have scanned the local directory for hardcoded credentials. The scanner identified 3 high-risk findings across your configuration and source files. All values in the report below have been redacted to prevent further exposure.

    Secrets Scan Results

    File PathTypeRisk LevelPattern Match (Redacted)
    config/services.yamlAWS Access KeyCRITICALAKIA...[REDACTED]
    .env.developmentSlack Bot TokenHIGHxoxb-...[REDACTED]
    src/auth/helper.pyPrivate Key (PEM)HIGH-----BEGIN RSA...[REDACTED]

    Remediation Steps Required:
    1.

    Rotate Credentials: The AWS Access Key and Slack Bot Token must be revoked and re-issued immediately through their respective provider consoles.
    2.

    Scrub History: Since these were found in the file tree, use git filter-repo or BFG Repo-Cleaner to remove these strings from all historical commits.
    3.

    Environment Variables: Move the Slack token from .env.development to a secure vault or encrypted environment variable store.

    Next steps

    • Run jwt token risk analyzer to inspect the scope of the found JWTs.
    • Use github actions workflow auditor to check if these secrets are being logged in CI.
    • Add false positives to your allowlist or use # secretscanner:allow for verified mocks.

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

    About this skill

    Find committed API keys and private keys before attackers do — values stay redacted.

    A single leaked ghp_ or AKIA key is enough. This skill walks a file or directory with gitleaks-style patterns for AWS keys, GitHub/GitLab PATs, Slack tokens/webhooks, Stripe live keys, Google API keys, npm/PyPI tokens, JWTs and PEM private keys. Reports redact the secret values.

    What it does

    • Skips .git, node_modules, binaries and common lock/build dirs
    • Allowlist file or # secretscanner:allow per line for false positives
    • Markdown + CSV; exit 0 when clean

    Who it's for

    Developers and security engineers scanning a repo checkout or a suspicious .env before it ships.

    Limits

    Regex heuristics — expect some false positives; always rotate anything real and scrub git history. Not legal advice.

    What's included

    • SKILL.md: workflow, commands, how to explain findings
    • scripts/: the checker (stdlib Python) plus shared seccommon.py
    • references/sources.md: specs and guidance cited
    • examples/: good and bad samples used in the demo
    • tests/: unit tests (Python 3.8 / 3.9 / 3.13)

    Standard-library Python only. No API keys, no network calls, no installs.

    • Offline / local files only — does not fetch live URLs or call cloud APIs.
    • Heuristic checks; not a full substitute for a professional audit or pentest.
    • Not legal advice and not a certification of compliance.

    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

    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 20 days ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    secrets-pattern-scanner/**

    Fully offline. No subprocess, no network modules used for outbound calls, no credential access.

    Listed20 days ago

    What's inside

    Frequently Asked Questions

    No. Reports redact secrets (prefix…suffix + length). Context lines are redacted too.

    New in Security