security-audit · git:20261014.09fa56a · 2026-10-14 · sha256 18bed5a79aa58584

security-audit git:20261014.09fa56aA

Immutable. This exact content never changes and is served at /api/v1/blob/18bed5a79aa58584.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_c4bggwljr2pmt4qs/18bed5a79aa585842c89a7ee95ed5740df79411ddca0ca211df9d3fe0eef8259.json

Then /plugin install security-audit@markdownregistry-c4bggwljr2pmt4qs in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: security-audit
description: "Comprehensive code security audit: OWASP Top 10, CWE mapping, SAST/DAST methodology, and structured findings with CVSS scoring."
---

# Security Audit Skill

Systematic security code review methodology.

## Process

1. **Scope** — identify entry points, trust boundaries, and data flows
2. **Map** — trace user input from source to sink
3. **Classify** — map each finding to CWE and OWASP Top 10 categories
4. **Score** — assign CVSS v3.1 severity (Critical/High/Medium/Low/Info)
5. **Exploit** — write a concrete proof-of-concept for each finding
6. **Report** — structured findings with severity, location, evidence, and remediation

## OWASP Top 10 Coverage

- A01: Broken Access Control
- A02: Cryptographic Failures
- A03: Injection (SQL, NoSQL, OS, LDAP)
- A04: Insecure Design
- A05: Security Misconfiguration
- A06: Vulnerable Components
- A07: Authentication Failures
- A08: Data Integrity Failures
- A09: Logging & Monitoring Failures
- A10: Server-Side Request Forgery

## Output Format

For each finding provide:
- **Title**: short descriptive name
- **Severity**: Critical / High / Medium / Low / Info
- **CWE**: CWE-ID and name
- **Location**: file:line
- **Evidence**: code snippet showing the vulnerability
- **Impact**: what an attacker can achieve
- **Remediation**: specific code fix