Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Freebies — Secret Regex Checker

    1

    Scan repositories and config files for hardcoded API keys, tokens, and database secrets using entropy and regex.

    Free

    Security scanned
    Freebies — Secret Regex Checker

    Freebies — Secret Regex Checker

    Example session with this skill installed

    Scan the current directory for any hardcoded API keys or database strings and suggest how to fix them.

    • Read your context and instructions
    • Compiled the freebies

    I have completed a scan of the project directory. I identified three potential credential exposures using regex signatures and entropy analysis. All values have been masked to prevent further exposure.

    Secret Detection Report

    File PathTypeRisk LevelFound Pattern (Masked)Mitigation
    src/config/db.jsDatabase URICriticalmongodb+srv://admin:********@cluster0.abc.netUse process.env.DB_URI
    scripts/deploy.shAWS Access KeyHighAKIA************7QUse AWS_ACCESS_KEY_ID
    src/lib/stripe.tsStripe Secret KeyHighsk_live_**********4a9Use STRIPE_SECRET_KEY

    Recommended Remediation Commands

    To move these secrets to your environment, create or update your .env file and use the following export pattern:

    
    # 1. Add to .env file
    echo "DB_URI=your_real_password_here" >> .env
    echo "AWS_ACCESS_KEY_ID=your_real_key_here" >> .env
    echo "STRIPE_SECRET_KEY=your_real_token_here" >> .env
    
    # 2. Add .env to .gitignore to prevent future leaks
    echo ".env" >> .gitignore
    

    Next steps

    • Move the identified strings to a secure .env file.
    • Rotate the compromised credentials immediately as they may have been cached in git history.
    • Run git rm --cached on any files that previously contained these secrets.

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

    About this skill

    Hardcoded secrets in your codebase are a ticking time bomb for production security. This skill acts as a credential sentinel, scanning your repository files and commit diffs to catch plaintext API keys, tokens, and database credentials before they reach version control.

    What it does

    • Multi-Service Scanning identifies signatures for AWS, GitHub, Stripe, OpenAI, and other cloud providers.
    • Entropy Analysis uses Shannon entropy calculations to detect high-randomness strings that regex might miss.
    • Automatic Masking ensures that detected secrets are redacted in reports to prevent further exposure.
    • Mitigation Guidance generates specific environment variable commands to help you move secrets out of code.
    • Environment Auditing checks configuration files and connection strings for hardcoded passwords.

    How it works

    1. Target Identification specifies the files, directories, or recent git diffs you want to analyze.
    2. Signature Matching runs the scan using a combination of regex patterns and entropy checks.
    3. Redaction & Reporting generates a summary of findings with all sensitive values masked.
    4. Remediation provides the exact commands needed to transition to safe environment variables.

    Frameworks & tools

    The skill performs static analysis on project files using regex and Shannon entropy logic. It is designed for use with local project environments and version control systems like Git.

    Why this beats prompting it yourself

    Generic prompts often fail to distinguish between random strings and actual keys, leading to high false positives. This skill applies specific entropy thresholds and known provider patterns while enforcing strict masking rules to keep your logs clean.

    Use cases

    • Auditing a legacy repository for hardcoded database credentials.
    • Scanning a git diff before committing code to ensure no keys were left in.
    • Validating .env file safety and ensuring secrets aren't in config files.
    • Checking CI/CD configuration files for exposed cloud provider tokens.

    Known limitations

    Restricted to the active project workspace. It cannot access system-level configuration paths or parent directories. Plaintext secrets are never displayed in full.

    Restricted to scanning the active project workspace only. Will not display raw plaintext secrets in output; all findings are masked for security.

    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

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 4 days ago

    • Free with an Agensi account

    Requires

    Config Auth Auditor MCP
    File System Read/Write (strictly scoped to current project workspace `./`). Zero global installation or elevated privileges required.

    Permissions

    Read Files
    Network Access

    Target Use Cases: - Scan my project for leaked API keys or passwords. - Check this commit diff for accidental secrets before pushing. - Verify our .env and config files don't leak private tokens.

    Listed4 days ago

    What's inside

    Frequently Asked Questions

    This skill acts as a security sentinel by scanning your code and config files for hardcoded API keys and tokens. It solves the risk of accidental credential exposure by using both pattern matching and entropy analysis to find secrets that standard search tools often miss.

    The skill includes pre-built signatures for major providers like AWS, Stripe, GitHub, and OpenAI. Beyond these specific patterns, its entropy analysis detects high-randomness strings, allowing it to identify proprietary or unconventional tokens from other services.

    This skill is designed for use within AI agent platforms that support local file system access and static analysis. It works seamlessly with any agent that can interact with your Git workspace or project directories.

    Security is a priority; the skill automatically masks detected secrets in its reports. It provides the location of the vulnerability and instructions on how to migrate the secret to an environment variable without ever displaying the full plaintext key in your logs.

    You receive the full secret-scanning logic, the entropy calculation engine, and a library of regex patterns for cloud providers. It also includes the remediation module which generates commands to help you transition from hardcoded strings to secure environment variables.

    New in Security