Security Secrets Specialist

Detects hardcoded credentials and leaked secrets in code, configuration, and git history.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/htxryan/claude-code-config-profiles --skill security-secrets-specialist-htxryan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Security Secrets Specialist
Source: https://github.com/htxryan/claude-code-config-profiles/tree/main/.agents/skills/compound/agents/security-secrets
Command: npx skills add https://github.com/htxryan/claude-code-config-profiles --skill security-secrets-specialist-htxryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hardcoded API keys, passwords, and tokens committed to repositories create serious security exposure. This Skill scans code and configuration for credential patterns, entropy anomalies, and secrets buried in git history before they become breaches. ## Core Features & Use Cases - Pattern-Based Detection: Matches known key formats such as AWS AKIA keys, GitHub ghp_ tokens, Slack xoxb/xoxp tokens, and JWT signatures, plus suspicious variable names like password, apiKey, and connection_string. - Entropy and Hiding-Spot Analysis: Flags high-entropy strings in assignment contexts and checks common leak locations including committed .env files, Docker ENV/ARG instructions, and CI workflow files. - Git History Auditing: Searches deleted env files and historical diffs for previously committed secrets, while distinguishing real credentials from safe test fixtures and placeholders. - Use Case: During a code review, spawn this specialist to scan all changed files, receive severity-classified findings (P0-P3) with masked value previews, and route results to the security-reviewer for remediation. ## Quick Start Ask the agent to scan the current branch's changed files and git history for hardcoded secrets and report any findings with severity ratings.

Frequently Asked Questions about Security Secrets Specialist

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

FAQPage Schema
How do I scan code for hardcoded secrets and API keys?▼

Scan changed files for credential variable names like password, token, and apiKey, match known key formats such as AWS AKIA and GitHub ghp_ tokens, and flag high-entropy strings in assignment contexts. This Skill automates all three checks and reports findings by severity.

How to find secrets committed in git history?▼

Use git log --diff-filter=D on env file patterns to find deleted credential files, and git log -p on specific files to inspect historical changes to secret-like values. Deleted secrets still exist in history and must be rotated, not just removed.

Does secrets scanning flag test fixtures and placeholder values?▼

No. Values prefixed with test_, fake_, or mock_, placeholders like YOUR_API_KEY_HERE or changeme, and public keys are recognized as safe patterns and excluded from findings. Everything else is flagged for review.

What severity levels are used for detected secrets?▼

Findings are classified as P0 for real credentials, P1 for likely credentials, P2 for suspicious patterns, and P3 for missing .gitignore entries on secret files. Each finding includes file location, matched pattern, and a masked value preview.

Where do secrets commonly hide outside of source code?▼

Common hiding spots include committed .env or .env.local files without gitignore rules, Dockerfiles with ENV SECRET or ARG PASSWORD instructions, CI configs like GitHub Actions workflows with inline secrets, and test fixtures using real-looking credentials.