Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    public mirror secret guard

    1

    Automated secret scanning and identity scrubbing for repositories mirrored to public GitHub.

    Free

    Security scanned
    public mirror secret guard

    public mirror secret guard

    Example session with this skill installed

    Audit my staged changes for a public mirror push. I have an updated .env and some Kubernetes values.yaml changes.

    • Read your context and instructions
    • Compiled the public mirror secret

    I have audited your staged changes using the scan_diff_guard.py script. The scan identified one missing configuration counterpart and verified that no internal hostnames were leaked in the diff.

    Security Audit Report

    File PathStatusAction Taken
    infrastructure/helm/values.yamlPASSNo internal hostnames or secrets detected in diff.
    .envIGNOREDFile is correctly listed in .gitignore.
    .env.exampleWARNINGMissing key STRIPE_SECRET_KEY found in .env.
    PROMPTLOG.mdPASSNo verbatim credentials found in markdown logs.
    AGENTS.local.mdPROTECTEDMachine state correctly isolated from tracked AGENTS.md.

    Detected Counterpart Mismatch

    The following keys exist in your git-ignored .env but are missing from .env.example:

    • STRIPE_SECRET_KEY
    • DB_INTERNAL_URL

    Next steps

    1. Sync .env.example by adding the missing keys with placeholder values.
    2. Move the cluster endpoint notes from README.md to AGENTS.local.md to ensure they stay off the mirror.
    3. Run uv run scripts/scan_diff_guard.py --staged again to confirm a clean bill of health before pushing.

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

    About this skill

    Managing a public repository mirror is high risk. One accidental commit of a Kubernetes secret or internal hostname creates a permanent security hole in your Git history. This skill enforces pre-commit hygiene to ensure sensitive data stays local and public mirrors remain clean.

    What it does

    • Diff-level scanning audits git diff --cached to catch secrets before they are committed, not just in the final file state.
    • Identity scrubbing removes upstream boilerplate slugs and brand names to prevent leaking project origins.
    • State separation mandates the use of git-ignored *.local.md files for machine-specific notes and cluster paths.
    • Counterpart parity ensures every ignored .env or values.yaml file has a matching .example template with identical keys.
    • Fail-closed enforcement halts the workflow immediately if suspicious tokens or internal hostnames are detected.

    How it works

    1. Run the scan_diff_guard.py script against staged changes to identify leaked credentials or banned strings.
    2. Generate .example files for all git-ignored configurations to maintain schema parity without exposing values.
    3. Migrate environment-specific deployment notes from tracked files into @AGENTS.local.md.
    4. Configure the --banned-brand flag to filter out upstream template identifiers during scaffolding.

    Frameworks & tools

    This skill integrates with Git for diff analysis, uses uv for script execution, and manages configuration files like values.yaml, .env, and Markdown logs.

    Why this beats prompting it yourself

    Manual prompts often miss secrets hidden in large diffs or forgotten upstream boilerplate references. This skill provides a systematic, script-driven audit that enforces file-level architectural rules like .local.md separation that LLMs usually overlook.

    Use cases

    • Auditing staged changes before pushing a private repo to a public GitHub mirror.
    • Scrubbing brand names and internal emails when scaffolding a new project from a boilerplate template.
    • Maintaining .env.example files automatically as local environment variables evolve.
    • Preventing PROMPTLOG.md or Kubernetes manifests from leaking internal infrastructure hostnames.

    Known limitations

    Requires uv to be installed for script execution. Scanning is limited to staged changes and does not retroactively clean existing Git history.

    Requires the uv package manager. Only scans staged changes via git diff --cached. Does not perform retroactive history cleaning of already pushed commits.

    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

    Python
    Git

    Permissions

    Terminal / Shell
    Read Files
    Listed4 days ago

    What's inside

    Frequently Asked Questions

    The skill audits staged Git changes in real-time, catching credentials and internal hostnames before they are committed, whereas standard scanners often only check files after they have already entered the Git history.

    Yes, it is designed to work within any environment where you can execute scripts. It uses 'uv' for fast, isolated execution, making it compatible with most AI agents and developer workflows.

    You will receive the 'scan_diff_guard.py' script, the configuration schema for identity scrubbing, and the documentation for setting up the '.local.md' state separation workflow.

    The skill is designed to prevent new leaks by scanning 'git diff --cached' before a commit occurs; it does not perform retroactive scrubbing of previously pushed commits or old Git history.

    Simply install 'uv', place the provided scripts in your repository, and configure your banned brand strings to begin auditing your staged changes and generating template files.

    It identifies missing '.example' files and alerts you if the keys in your '.env' or 'values.yaml' don't match their public templates, ensuring your mirror stays functional without being vulnerable.

    New in DevOps & Cloud