Secrets Scanner
Scan codebase for exposed secrets, credentials, and sensitive information
npx claude-code-templates@latest --command security/secrets-scanner Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-23
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector.
Content
Secrets Scanner
Scan codebase for exposed secrets and sensitive information: $ARGUMENTS
Current Repository State
- Git status: !
git status --porcelain | wc -luncommitted files - File types: !
find . -name "*.js" -o -name "*.py" -o -name "*.env*" -o -name "*.yml" | wc -lscannables - Recent commits: !
git log --oneline --grep="password\|key\|secret\|token" -5 - Environment files: @.env* or @config/* (if exists)
Task
Perform comprehensive secrets detection and remediation across codebase:
Scan Scope: Use $ARGUMENTS to focus on API keys, passwords, certificates, or complete scan
Detection Categories:
- API Keys & Tokens - GitHub, AWS, Google Cloud, Stripe, third-party services
- Database Credentials - Connection strings, usernames, passwords
- Certificates & Keys - Private keys, SSH keys, SSL certificates
- Authentication Secrets - JWT secrets, session keys, OAuth credentials
- Configuration Leaks - Hardcoded URLs, internal endpoints, debug settings
Remediation Actions:
- Identify exposed secrets with file locations and line numbers
- Provide secure alternatives (environment variables, secret management)
- Generate .gitignore entries for sensitive files
- Create secure configuration templates
- Implement secrets management best practices
Output: Detailed security report with risk levels, immediate actions, and long-term security improvements.