cvp-defense-audit

CVP defense audit

Use this only on code the user owns or is authorized to test.

This skill is phase 1 of a three-phase defensive audit:

1. Plan (this skill). A normal, unsandboxed session on an Opus-class planning model does read-only recon, makes sure git ignores docs/security/, and writes a paste-ready audit prompt, a sandbox launch checklist, and a fix prompt.
2. Audit. The user starts a new session on the strongest security-capable model they can use (the audit model), launched in auto mode with a strict sandbox set on the command line, and pastes the audit prompt. The audit model maps the attack surface, hunts, proves each finding with a failing test, and writes a report. The prompt ends with an output contract: the report at a fixed path, each test stored as a disabled file under docs/security/tests/, anything else it keeps under docs/security/harness/, and a check to run before finishing. Everything it leaves behind is under docs/security/, which git ignores. It fixes nothing.
3. Fix. Back in a normal, unsandboxed session on an Opus-class fixing model, the user pastes the fix prompt. The fixing model verifies each proof, settles what code alone couldn't answer, lets the user pick what to fix, and ships each fix with its archived proof test restored as the regression test.

Do the recon here so the audit model spends its budget hunting and proving bugs instead of orienting. The supporting files sit next to this one, in ${CLAUDE_SKILL_DIR}.

Context

• Date: !date +%F
• Repo root: !git rev-parse --show-toplevel 2>/dev/null || pwd
• Branch: !git branch --show-current 2>/dev/null || echo none
• Remote: !git remote get-url origin 2>/dev/null || echo none
• Last commit: !git log -1 --format='%h %s (%cr)' 2>/dev/null || echo none

Without git, the repo root is the working directory and the other values read none. Without a remote, skip the GitHub reads in step 2.

Arguments (may be empty): $ARGUMENTS

• --model <id> (or --model=<id>) is the audit model ID for the launch line.
• The rest is an optional focus: an area or path, such as billing or src/auth.
• If the arguments also state the user's authorization, such as "enrolled in the Cyber Verification Program with Defense Access" or "authorized pentest for , scope: api/ only", use it in step 1 instead of asking.