occam-auditlisted
Install: claude install-skill stephenoffer/occam
# Occam audit
Find what is actually wrong with code that already exists, say so with evidence, repair what you're allowed to, and ask about the rest. `occam` applies here too, so load it first if it isn't loaded: its authorization, evidence and honesty rules hold in every step.
Tools are in the `occam` skill's folder, at `scripts/occam.py` (from here, `../occam/scripts/occam.py`). `scan`, `map`, `query` and `deps` never run or import the code they read. `golden`, `mutate`, `bench`, `goal verify` and `tools --allow-exec` do run things, so read what they'll run first. Below, `occam X` means `python3 <that path> X`.
## Done means
An audit is done when:
- Every finding you report has a location, the input or state that triggers it, what goes wrong and your evidence. A scanner hit you didn't confirm is labeled a lead.
- You ran `occam scan`, even if you read every line, went through each category in its summary, and confirmed or dismissed every critical and high lead. Say how many others you skipped.
- You read the paths where input, money, auth, tenancy and data writes meet. On code too large to read, take the riskiest and name the rest. "Not checked" is for what you couldn't reach, not what you didn't get to.
- You state the assumed workload, because scale problems only mean something against one.
- You state what you did not read or could not run.
- If you repaired anything, each batch was verified, and you listed every change to what users see or pay, separately from the