A structured review command for a completed software plan. It checks the plan from both a senior-engineering and compliance perspective before implementation begins.

Use it after planning to review PLAN.md, classify findings by urgency, update the plan with important corrections, and create an AUDIT.md report.

It helps catch important design, risk, and compliance issues before work is applied to the codebase.

paul:audit — Command for coding agents by ChristopherKahler: A structured review command for a completed software plan.

Install

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.

agentmods

npx agentmods add commands/christopherkahler/paul/audit

Clone the repo

git clone --depth 1 https://github.com/ChristopherKahler/paul

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/christopherkahler/paul/audit.svg)](https://agentmods.dev/commands/christopherkahler/paul/audit)

Your own site

<a href="https://agentmods.dev/commands/christopherkahler/paul/audit"><img src="https://agentmods.dev/badge/commands/christopherkahler/paul/audit.svg" alt="Measured on agentmods" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 460 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What 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.00013	$0.00460
Opus 5	$0.00006	$0.00230
Sonnet 5	$0.00003	$0.00092
Haiku 4.5	$0.00001	$0.00046

Measured 4d ago against content hash f2628e4c3d5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

paul:audit 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 4d 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.

src/commands/audit.md · 58 lines

What it actually says

When to use: After PLAN phase complete, before APPLY. Optional: Only runs when explicitly invoked or suggested by enterprise_plan_audit config. Who audits: Claude performs the audit assuming the role of senior principal engineer + compliance reviewer.

<execution_context> @~/.claude/paul-framework/workflows/audit-plan.md </execution_context>

@.paul/STATE.md @.paul/config.md

The workflow implements:

Validate preconditions (PLAN exists, loop at PLAN complete)
Load and parse the PLAN.md
Execute enterprise audit (6-section structured review)
Classify findings (must-have, strongly-recommended, can-safely-defer)
Auto-apply must-have and strongly-recommended findings to PLAN.md
Create AUDIT.md report in phase directory
Update STATE.md with audit completion
Present summary and route to APPLY

<success_criteria>

PLAN.md audited against enterprise standards
Must-have and strongly-recommended findings applied to PLAN.md
AUDIT.md report created in phase directory
STATE.md updated to reflect audit completion
User presented with next action (run APPLY) </success_criteria>

<anti_patterns>

Don't invent requirements not implied by the plan
Don't assume "future phases" will fix gaps
Don't say "this is fine for v1" unless justified
Don't optimize for politeness over correctness
Don't skip applying findings - the whole point is automatic remediation </anti_patterns>

Changes

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.

4d ago First seen · 58 lines · 13 tokens per session scan A f2628e4c3d5a

Subscribe to this mod's changes

paul:audit is a command published in the GitHub repository ChristopherKahler/paul (1,212 stars, last pushed 13d ago), licensed MIT. It adds 13 tokens to every session and 460 once invoked, about $0.0001 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-30.

Code review Planning ai-development ai-tools claude claude-code development-framework project-orchestration

paul:audit

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

safe-refactor

security-review

test

implement-spec

refactor

deploy_to_docker