Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Secret Leak Scan

    1

    Statically scan directories and .asar archives for leaked API keys, tokens, and private keys before deployment.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Secret Leak Scan

    Secret Leak Scan

    Example session with this skill installed

    Scan my ./dist folder for any leaked API keys or credentials before I deploy to production.

    • Read your context and instructions
    • Compiled the secret leak scan
    • Generated the document

    Secret scan completed for the ./dist directory. The scan inspected 42 files and skipped 2 files due to size limits.

    Secret Leak Scan Report

    TypeFile:LineFingerprintRemediation
    aws-access-key-iddist/assets/config.js:14AKIA... (len=20, sha256:8f3a1...)Rotate AWS IAM user keys immediately.
    stripe-live-keydist/server/main.js:204sk_live... (len=32, sha256:c4d2e...)Deactivate key in Stripe Dashboard; check logs.
    private-key-blockdist/certs/dev.pem:1-----BEGIN... (len=1600, sha256:a9b1c...)Revoke certificate and remove from bundle.

    Notes

    • dist/assets/large-assets.bin skipped (exceeds 5 MB).
    • dist/docs/examples.html contained 1 suppressed documentation placeholder.

    Next steps

    1. Rotate credentials: Revoke the AWS and Stripe keys at their respective provider consoles immediately.

    Clean source: Locate the source files that produced these artifacts and move the hardcoded values to environment variables.
    3.

    Update ignore lists: Add dist/certs/ to your .gitignore and confirm your build script isn't pulling in development secrets.
    4.

    Audit history: Run git log -S with these fingerprints to see if they were committed to your repository history.

    examples.html

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    Your build artifacts and repository history might contain plaintext credentials that lead to immediate account takeovers. This skill performs static analysis on project directories, build outputs, and Electron .asar archives to find leaked secrets before they are committed or released.

    What it does

    • Multi-format scanning analyzes source code, minified build artifacts, and packed .asar bundles.
    • Credential detection identifies AWS keys, GitHub PATs, Slack tokens, Stripe live keys, and Google API keys.
    • Private key auditing flags exposed private key blocks often found in SSH or SSL configurations.
    • Safe reporting generates JSON findings with masked fingerprints to prevent further exposure of raw values.
    • Triage assistance maps findings to specific files and lines with clear rotation instructions.

    How it works

    1. Target selection involves specifying the project root, a distribution folder like dist/, or a packaged app bundle.
    2. Analysis execution runs the bundled Node.js script to perform pattern matching across the file tree.
    3. Report processing parses the resulting JSON to count findings and categorize them by service type.
    4. Remediation delivery produces a prioritized list of leaked credentials and rotation steps.

    Frameworks & tools

    The scanner requires Node.js 18 or later. It uses @electron/asar for archive inspection and is compatible with any CI/CD environment that supports custom shell scripts and exit codes.

    Why this beats prompting it yourself

    Generic prompts often miss secrets hidden in large minified files or binary archives. This skill uses a dedicated script for consistent pattern matching and provides a structured remediation workflow that treats every match as a high-priority security event.

    Use cases

    • Pre-commit checks to prevent developers from pushing plaintext API keys to remote repositories.
    • Release auditing to ensure production build folders don't contain sensitive config files.
    • Electron app hardening by scanning packed .asar files for accidentally bundled environment variables.
    • Post-incident cleanup by identifying which credentials were leaked and require immediate rotation.

    Known limitations

    Static analysis cannot detect secrets split across lines or custom token formats. It does not check historical git commits unless the files currently exist in the working tree.

    Requires Node 18+. Cannot detect secrets split across multiple lines. Only scans current files, not full git history. Requires @electron/asar for .asar archives.

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

    Requires

    Node.js 18+
    @electron/asar
    Node.js
    Git

    Permissions

    Terminal / Shell
    Read Files

    Static, read-only scan of local files and .asar archives. No network calls; the JSON report is printed to stdout.

    Listed1 month ago
    Updated27 days ago

    What's inside

    Frequently Asked Questions

    The skill scans standard project directories, build output folders (like `dist/` or `build/`), and specifically supports Electron `.asar` archives to find secrets hidden within packaged applications.

    While optimized for modern LLMs that can interpret JSON security reports, it requires a Node.js 18+ environment to execute the core scanning engine on your local machine or CI/CD runner.

    Upon purchase, you receive the scanning logic, the triage reporting module, and a pre-configured workflow that guides your AI agent through the detection and remediation process.

    No, the scanner generates a local JSON report with masked fingerprints, ensuring that your raw credentials are never sent to an external LLM or AI provider during the analysis phase.

    This skill performs static analysis on current files and build artifacts; it does not scan your entire Git history or deleted commits, which may require a dedicated repository forensic tool.

    The skill is designed as a standalone security module that can be integrated into pre-commit hooks or automated deployment pipelines to block releases if a leak is detected.

    New in DevOps & Cloud