PAUL is a structured development workflow for Claude Code that organizes AI-assisted work into planning, implementation, and state-reconciliation steps. It is for developers who want acceptance criteria, managed context, and completed plans while building software with Claude Code. Its catalogue entries are commands that implement the workflow.
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 commands/christopherkahler/paul/discussgit clone --depth 1 https://github.com/ChristopherKahler/paulWrote 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.
[](https://agentmods.dev/commands/christopherkahler/paul/discuss)<a href="https://agentmods.dev/commands/christopherkahler/paul/discuss"><img src="https://agentmods.dev/badge/commands/christopherkahler/paul/discuss.svg" alt="Measured on agentmods" height="20"></a>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.00207 |
| Opus 5 | $0.00006 | $0.00103 |
| Sonnet 5 | $0.00003 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
paul:discuss 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 5d 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.
What it actually says
When to use: Before planning a phase, when goals and approach need exploration.
<execution_context> @~/.claude/paul-framework/workflows/discuss-phase.md </execution_context>
@.paul/PROJECT.md @.paul/STATE.md @.paul/ROADMAP.md
<success_criteria>
- CONTEXT.md created in phase directory
- Goals and approach articulated
- Ready for /paul:plan command </success_criteria>
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.
- 5d ago First seen · 35 lines · 13 tokens per session scan A cfa8e960d7b2
paul:discuss is a command published in the GitHub repository ChristopherKahler/paul (1,216 stars, last pushed 14d ago), licensed MIT. It adds 13 tokens to every session and 207 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.
Other commands, from other repositories
safe-refactor
Safe refactoring with automated review, testing, and rollback capabilities.
security-review
Comprehensive security analysis with multi-layer vulnerability detection.
test
Smart test runner with filtering, coverage, and health monitoring.
implement-spec
Implement specification with full traceability and test-driven development.
refactor
Interactive refactoring assistant based on Martin Fowler's refactoring catalog.
deploy_to_docker
Build Docker image and start/redeploy the MCP Task Orchestrator container, reusing the last-used config by default.