env-secrets-manager

Scan repositories for leaked secrets and guide credential rotation workflows.

2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/BryanPinheiro77/FinanceBot-BackEnd --skill env-secrets-manager-bryanpinheiro77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: env-secrets-manager
Source: https://github.com/BryanPinheiro77/FinanceBot-BackEnd/tree/main/.agents/skills/env-secrets-manager
Command: npx skills add https://github.com/BryanPinheiro77/FinanceBot-BackEnd --skill env-secrets-manager-bryanpinheiro77

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Hardcoded credentials, committed .env files, and stale secrets are among the most common causes of security incidents. This Skill audits repositories for likely secret leaks, classifies findings by severity, and provides concrete guidance for rotation, prevention, and CI/CD secret handling. ## Core Features & Use Cases - Secret Leak Detection: Run the bundled Python auditor to scan env files and source code for patterns like AWS keys, GitHub tokens, Slack tokens, private key blocks, and JWTs, with severity-ranked findings and JSON output for CI pipelines. - Rotation & Incident Response: Follow step-by-step playbooks for emergency credential rotation, git history scanning, and secret removal using tools like git filter-repo, gitleaks, and truffleHog. - Prevention & Hardening: Set up pre-commit hooks with gitleaks or detect-secrets, validate required environment variables at startup, and choose the right cloud secret store (Vault, AWS Secrets Manager, Azure Key Vault, GCP Secret Manager). - Use Case: Before pushing a commit that touched config files, run the auditor on your repo, review critical findings, rotate any real credentials, and add a pre-commit hook so leaks are blocked before they reach version control. ## Quick Start Scan my repository for leaked secrets and show me the critical findings with recommended rotation steps.

Frequently Asked Questions about env-secrets-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan a repository for leaked secrets?▼

Run the bundled env_auditor.py script against your repository root to scan env files and source code for common secret patterns. It reports findings with severity levels and supports JSON output for CI pipeline integration.

What secret patterns does the auditor detect?▼

The auditor detects OpenAI-style keys, GitHub personal access tokens, AWS access key IDs, Slack tokens, private key PEM blocks, generic secret assignments, and JWT-like tokens. Findings are classified as critical, high, or medium severity.

gitleaks vs detect-secrets for pre-commit scanning?▼

gitleaks uses regex rules with a .gitleaksignore file for false positives, while detect-secrets uses a baseline file with an interactive audit workflow. Both integrate with the pre-commit framework and are documented in this Skill.

What should I do when a secret is leaked in git history?▼

Immediately revoke the credential at the provider, deploy a replacement to all consumers, then remove the value from history using git filter-repo. Audit access logs for unauthorized use during the exposure window and file an incident report.

Which cloud secret manager should I use for production?▼

Use the cloud-native option (AWS Secrets Manager, Azure Key Vault, GCP Secret Manager) for single-cloud workloads due to tight IAM integration. Choose HashiCorp Vault for multi-cloud or hybrid environments needing dynamic secrets.

Does the secret scanner work in CI pipelines?▼

Yes, the auditor supports a --json flag that outputs structured findings suitable for CI gates. You can fail builds on critical or high severity findings and combine it with pre-commit hooks for layered defense.