Skip to content
Back to skills

Security Cleanup

ASecurity

Applies fixes for security findings produced by /security-review. Use when the

  • 20 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 9, 2026
securitypythongojavaapisecurity

Works with

  • api

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add thejefflarson/soundcheck --skill security-cleanup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Security Cleanup?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Security Cleanup
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thejefflarson-security-cleanup/badge)](https://www.skillsdirectory.com/skills/thejefflarson-security-cleanup)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: security-cleanup
description: Applies fixes for security findings produced by /security-review. Use when the
  user wants to fix security issues found by /security-review or when they ask
  to clean up, remediate, or apply fixes for security findings.
---

# Security Cleanup (A01:2025–A10:2025 + LLM01:2025–LLM10:2025)

## 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

1. Get the findings: from the user's message, a recent `/security-review`
   output, or — if none are available — run `/security-review` first to
   produce them.

2. For each finding (highest severity first):
   - Read the cited file at the cited line
   - Read `.claude/skills/<skill>/SKILL.md` for the correct fix pattern
   - Apply the fix using the Edit tool
   - Use the language's idiomatic safe API (Go `html/template`, Python
     `Environment(autoescape=True)`, Java `PreparedStatement`, etc.)

3. 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

- CWE-693 ([Protection Mechanism Failure](https://cwe.mitre.org/data/definitions/693.html))
- [OWASP Web Top 10:2025](https://owasp.org/www-project-top-ten/)
- [OWASP LLM Top 10:2025](https://owasp.org/www-project-top-10-for-large-language-model-applications/)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.