Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/sturec5/code-audit-protocol/audit-protocolnpx skills add sturec5/code-audit-protocol --skill audit-protocolgit clone --depth 1 https://github.com/sturec5/code-audit-protocolWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00133 | $0.01650 |
| Opus 5 | $0.00067 | $0.00825 |
| Sonnet 5 | $0.00027 | $0.00330 |
| Haiku 4.5 | $0.00013 | $0.00165 |
Grade A, and why
audit-protocol scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Protocol
The taxonomy is ${CLAUDE_PLUGIN_ROOT}/AUDIT_PROTOCOL.md — an absolute path by
the time you read this. If that path does not resolve, the same file is two
directories above the base directory stated when this skill loads.
Read it before auditing — do not audit from memory of it, and do not restate its phases back to the user. If you cannot read it, say so and stop: an audit run from memory of the taxonomy is not this protocol and must not be reported as one.
If the project under audit keeps its own copy of this taxonomy, read that copy instead and say which you used: it is pinned to the project and may have been amended, while the plugin's is identical everywhere.
That is a different thing from a project that keeps its own audit document — overlays, a triage table, a chosen subset of phases, house rules. That one does not replace the taxonomy, it layers on top. Read both: run its overlays first, take phase selection from it, and take what each phase actually checks from here. "The project's file wins" is about two copies of one document drifting apart. Applied to a project's own audit layer it reads as permission to skip the taxonomy, which is the audit-from-memory outcome the paragraph above forbids.
The phase numbers are a catalog, not a running order. Select through the triage table, and prefer the shallow member of a paired phase at T2 over running both.
Running an audit
1. Establish scope before looking at anything.
Audit one bounded change, feature, module, service, or user journey. A large codebase declared "reviewed" after a scan is the failure this protocol exists to prevent. If the request does not name a scope, choose one and say which you chose. Record: what is under review, the revision, the intended outcome, the data classifications involved, and the trust boundaries crossed.
Then name your evidence sources before choosing a single phase: which of the repository, a running test seat, read access to the deployed environment, and production telemetry you have — and which you do not. A source you never named is a source you will not notice missing. You will run the phases that need it from the code alone and report them as passed.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 142 lines · 133 tokens per session scan A 57cafa6721db
audit-protocol is a skill published in the GitHub repository sturec5/code-audit-protocol (6 stars, last pushed 19d ago), licensed MIT. It adds 133 tokens to every session and 1,650 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
software-code-review
Evaluate source code for correctness, quality, security, style conformance, and maintainability, producing a structured review report with findings and recommendations. Use when the user wants to review, critique, audit, evaluate, or inspect source code — checking for bugs, logic errors, unhandled error paths…
juror-review
Inspect Juror Cloud PR findings and, only after an explicit confirmation, start or rerun a hosted Juror review.
logic-review
Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this…
logic-fix-all
Autonomous repository-wide audit-and-fix pipeline: health → review → locate/explain → fix → diff-verify → iterate until clean. Starts with a mandatory consent prompt (token-intensive); after consent runs hands-free. Trigger when the user wants ALL logic issues found and fixed — "fix everything", "fix all logic…
run-iteration-eval
Run the Logic-Lens content-eval pipeline for one iteration and produce a scored summary.json — use to measure a skill change. Wraps scripts/run-content-evals.sh (runner, costs tokens) and scripts/grade-iteration.py (grader, free, re-runnable). ALWAYS sync the plugin cache first. Use when the user wants to "run the…
logic-health
Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where…