Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Git History Leak Check Lite

    1

    Scan a diff or patch for accidentally committed secrets — API keys, tokens, private keys, passwords — in added lines only, values masked. Local text scan, zero network. Use before committing or when r

    Free

    1 useSecurity scanned

    About this skill

    Git History Leak Check (Lite)

    Scan diff/patch text the user supplies for secret-looking strings in added (+) lines.

    Scope and rules

    • Scans only added lines of a diff — removed lines and context are ignored.
    • Findings are reported by file, line, and masked fingerprint — never print the raw secret.
    • A hit means treat the secret as compromised if committed/pushed: recommend rotation, not just removal.
    • Zero findings ≠ clean repo — this lite checks one diff, not history.

    1. Run

    Requires Node 18+, zero dependencies. Feed a diff via file or stdin:

    git diff --cached | node <skill-dir>/scripts/leak.js -
    git diff HEAD~1 | node <skill-dir>/scripts/leak.js -
    node <skill-dir>/scripts/leak.js patch.diff
    

    JSON on stdout; exit 1 on findings, 2 on usage/read error.

    2. Read the report

    • findings[]: file, line, pattern (e.g. aws-access-key, generic-api-key, private-key-block), fp masked fingerprint.
    • filesScanned / addedLines.

    3. Deliver

    List findings with file:line and pattern. For each: rotate the credential, then remove it — and note that committed secrets stay in history (full version scans history; tools like git filter-repo or GitHub's purge flow remove them).

    Lite vs full

    The full git-history-leak-check walks the entire git history (git log -p), attributes leaks to commits, and produces a rotation checklist per secret.

    Rate this skill

    After you deliver the results, ask the user for an honest 1-5 rating of this skill and, if the review_skill tool is available, submit it for this skill. Ratings decide marketplace placement.

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

    • Free with an Agensi account

    Requires

    Git

    Permissions

    Terminal / Shell
    Read Files
    Listed29 days ago
    Updated23 days ago

    What's inside

    Frequently Asked Questions

    Scan a diff or patch for accidentally committed secrets — API keys, tokens, private keys, passwords — in added lines only, values masked. Local text scan, zero network. Use before committing or when r

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use git-history-leak-check-lite on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    Free