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/axiomantic/spellbook/advanced-code-review-plangit clone --depth 1 https://github.com/axiomantic/spellbookWrote 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/axiomantic/spellbook/advanced-code-review-plan)<a href="https://agentmods.dev/commands/axiomantic/spellbook/advanced-code-review-plan"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/advanced-code-review-plan.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.00019 | $0.04405 |
| Opus 5 | $0.00010 | $0.02202 |
| Sonnet 5 | $0.00004 | $0.00881 |
| Haiku 4.5 | $0.00002 | $0.00441 |
Grade A, and why
advanced-code-review-plan 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.
How it starts
The opening of the file, as written. The whole thing — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 1: Strategic Planning
Invariant Principles
- Risk-based prioritization: Higher risk files are reviewed first. Security, payment, and migration files take precedence over tests and documentation.
- Scope clarity: All files in scope must be identified before review starts. No file should be discovered mid-review.
- Complexity honesty: Estimates must reflect actual review effort required. Underestimating leads to rushed reviews; overestimating wastes planning time.
Purpose: Establish review scope, categorize files by risk, compute complexity estimate, and create prioritized review order.
1.0 Constants and Configuration
These constants are established at planning time and consumed across every phase.
Severity Order
SEVERITY_ORDER = {
"CRITICAL": 0, "HIGH": 1, "MEDIUM": 2, "LOW": 3, "NIT": 4, "QUESTION": 5, "PRAISE": 6
}
CRITICAL is reserved for security vulnerabilities, data loss, and production
outages. Bugs are HIGH, never CRITICAL.
Configurable Thresholds
| Threshold | Default | Consumer |
|---|---|---|
STALENESS_DAYS |
30 | /advanced-code-review-context 2.1 — discover_previous_review discards a review older than this |
LARGE_DIFF_LINES |
10000 | /advanced-code-review-plan 1.6.1 — plan_chunks line budget per chunk |
SUBAGENT_THRESHOLD_FILES |
20 | /advanced-code-review-plan 1.6.1 — plan_chunks file count that triggers chunked dispatch |
VERIFICATION_TIMEOUT_SEC |
60 | Phase 4 circuit breaker — verification exceeding this stops the run |
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 · 470 lines · 19 tokens per session scan A 4647bb933817
advanced-code-review-plan is a command published in the GitHub repository axiomantic/spellbook (10 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 4,405 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
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
boldguy-linkedin-answer
Draft a LinkedIn comment on a post, referencing the guide's relevant section, in Flow style with AI markers removed.
security-audit
Comprehensive security audit of your project AND Claude Code configuration. Analyzes secrets exposure, injection surfaces, dependencies, hook security, and produces a scored security posture assessment.
audit-quiz-coverage
Find quiz coverage gaps from recent guide/CHANGELOG/CC-releases changes and propose new questions.
worktree
Create a git worktree for isolated feature/fix work.
sync
Check guide/landing synchronization status.