Security Cleanup (A01:2025–A10:2025 + LLM01:2025–LLM10:2025)
SkillSecurityApplies fixes for security findings produced by /security-review. Use when the
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Security Cleanup (A01:2025–A10:2025 + LLM01:2025–LLM10:2025) skill
What this skill tells your AI
The instructions your AI receives, as published by thejefflarson/soundcheck in .claude/skills/security-cleanup/SKILL.md and read by ahel’s review.
What this checks
Applies fixes for security findings. Pair with /security-review to
detect issues, then /security-cleanup to fix them.
Vulnerable patterns
This skill remediates, not detects. Run /security-review first.
Procedure
-
Get the findings: from the user's message, a recent
/security-reviewoutput, or — if none are available — run/security-reviewfirst to produce them. -
For each finding (highest severity first):
- Read the cited file at the cited line
- Read
.claude/skills/<skill>/SKILL.mdfor the correct fix pattern - Apply the fix using the Edit tool
- Use the language's idiomatic safe API (Go
html/template, PythonEnvironment(autoescape=True), JavaPreparedStatement, etc.)
-
After all findings are processed, summarize what was fixed.
Rules:
- Never change observable behavior beyond removing the vulnerability
- If unsure about the correct fix, say so and skip that finding
- One Edit per finding — don't refactor surrounding code
Verification
- Each fix addresses the specific finding cited
- No fix introduces new vulnerabilities or changes business logic
- Summary lists all findings and their disposition
References
Signals
- GitHub stars
- 20
- Last commit
- Jul 2026
Advanced
- Catalog kind
- skill
- Gateway key
security-cleanup- Source
- github.com/thejefflarson/soundcheck