andrewyng/openworker/secret-scan
Claude Code and agent skill by andrewyng/openworker
- community
- ext:[{"type":"hook","description":"Pre/post lifecycle hooks"}]
Checking that the SKILL.md file is still in the repository.
Hunt committed secrets with gitleaks and drive safe rotation
Install
npx vskill@latest install andrewyng/openworker/secret-scanSemi-extensibleMentions customization, but needs skill-specific knowledge. Read the extensible skills standard
SKILL.md
The same SKILL.md was published earlier as andrewyng/openworker/secret-scan.
Find committed credentials and get them rotated and removed — without ever exposing them further yourself.
ABSOLUTE RULE: never print a secret's value — not in output, notes, todo items, commits, or PRs. Refer to every hit as "<kind> in <file>:<line> (commit <short-sha>)".
- Check the tool:
gitleaks version. If it's missing, do NOT skip this scan and do not
stop the review — ask for it with request_tool("gitleaks", …). If the user declines, or no pinned build exists for their platform, fall back to step 2b and say in your report that the sweep was manual.
- Scan working tree AND history — history matters most: a secret deleted in HEAD is still
live in every clone, and it is the hit users are most surprised by. a. With gitleaks: gitleaks detect --source . --report-format json --report-path /tmp/gitleaks.json b. Without it, do the same job by hand, and say so:
- working tree:
git grep -nIE '(api[_-]?key|secret|token|password|BEGIN [A-Z ]*PRIVATE KEY|AKIA[0-9A-Z]{16}|sk_(live|test)_[0-9a-zA-Z]{16,}|xox[baprs]-)' - history, including files deleted since:
git log -p --all -S 'AKIA' --pickaxe-all
and git log --diff-filter=D --name-only --pretty=format:%h -- '*.env*' '*credential*' '*secret*', then read the removed contents with git show <sha>^:<path>.
- Pipe anything you read through a redactor rather than into your transcript, e.g.
sed -E "s/[A-Za-z0-9_\\-]{16,}/[REDACTED]/g" — the no-printing rule still applies.
- Triage each hit by reading its context:
- Real credential, test fixture, or example placeholder? Say which and why.
- For real ones: what does it grant access to, and is it plausibly still valid?
- For every real secret, in this order:
a. ROTATE first — tell the user exactly where to revoke/rotate it (the provider's console page or CLI command). Rotation beats removal: history rewrite without rotation is false comfort. b. Remove it from the code: move to env vars or the project's secret store, matching how this codebase already handles configuration. c. Prevent recurrence: add/extend .gitignore for local secret files and offer a .gitleaks.toml baseline plus a pre-commit hook. d. History purge (git filter-repo/BFG) is DESTRUCTIVE and rewrites shared history — describe the trade-off and only proceed if the user explicitly asks.
- Deliver: a hit list (kind · location · verdict · rotation status), the cleanup
branch/PR, and the prevention setup you added or recommend.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingcoworker/personas/builtin/security/skills/secret-scan/SKILL.md
Popularity
- Repository stars
- 18,375
- Repository forks
- 2,598
- 7-day trend score
- 49
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Extension points
hookPre/post lifecycle hooks
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/andrewyng/openworker/secret-scan)