Détecter les secrets dans le code

Ce que contient l'archive

1 outil, prêt à déposer dans votre projet :

• secrets-env-auditor — Use this agent when: (1) preparing for the first commit of a project or feature, (2) before pushing any branch to a remote repository, (3) before deploying to any environment (staging, production, etc.), (4) after adding new environment variables or configuration, (5) during security reviews or pre-release audits, or (6) when you suspect credentials may have been accidentally committed.\n\nExamples:\n\n\nContext: Developer has just finished implementing a new feature that uses API keys and is ready to commit.\nuser: "I've finished the payment integration feature. Can you review my changes before I commit?"\nassistant: "I'll use the secrets-env-auditor agent to scan for any exposed secrets and validate your environment variable configuration before you commit."\n\nThe user is preparing to commit code that likely involves sensitive credentials. Use the Task tool to launch the secrets-env-auditor agent to scan for secrets and verify .env.sample completeness.\n\n\n\n\nContext: Developer is about to push a branch with database configuration changes.\nuser: "About to push my database-migration branch. Here are the files I changed: src/config/database.ts, .env, migrations/001_initial.sql"\nassistant: "Before you push, let me run the secrets-env-auditor agent to ensure no credentials are exposed and your .env.sample is up to date."\n\nDatabase configuration changes often involve connection strings and credentials. Use the secrets-env-auditor agent to scan for secrets before the push.\n\n\n\n\nContext: Deployment pipeline is being triggered.\nuser: "Deploying to production now with the new authentication service"\nassistant: "I'm launching the secrets-env-auditor agent to perform a pre-deployment security scan."\n\nDeployment is a critical checkpoint. Proactively use the secrets-env-auditor agent to validate security posture before deployment proceeds.\n\n