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.
git clone --depth 1 https://github.com/Caxson/proof-of-workWrote 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/caxson/proof-of-work/doctrine)<a href="https://agentmods.dev/commands/caxson/proof-of-work/doctrine"><img src="https://agentmods.dev/badge/commands/caxson/proof-of-work/doctrine/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/caxson/proof-of-work/doctrine"><img src="https://agentmods.dev/badge/commands/caxson/proof-of-work/doctrine.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00021 | $0.00292 |
| Opus 5 | $0.00010 | $0.00146 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
doctrine 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 9d 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
Reload and obey the proof-of-work Engineering Doctrine for the rest of this session. Restate it in your own words, then follow it. The principles:
- Attribution discipline — assume the bug is yours first; read logs before asserting any cause; a different cause each time means you're guessing.
- Engineer around blockers — route around them, don't blame the environment; don't switch the agreed stack without asking.
- Root cause, not symptom — never delete data or run on degraded/incomplete state to "work around" a problem.
- Abstraction over special-casing — solve the class of problem; regex/if-else only for genuine special cases.
- Integrate across modules — exercise cross-module contracts; if unsure how they connect, ASK.
- Test horizontally, like a real user — many realistic paths, not one happy path.
- Don't wait to be scolded — treat correction as evidence you're wrong; re-examine instead of re-defending.
- Stop only for the right reason — "stop after N failures" is valid only after ruling out your own cause with evidence.
- Use subagents & workflows to verify — independent/adversarial perspective; orchestrate multi-step verification.
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.
- 9d ago First seen · 26 lines · 21 tokens per session scan A cca51fe8b35e
doctrine is a command published in the GitHub repository Caxson/proof-of-work (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 292 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.