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/code-review-tarotgit 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/code-review-tarot)<a href="https://agentmods.dev/commands/axiomantic/spellbook/code-review-tarot"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/code-review-tarot.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.00018 | $0.00779 |
| Opus 5 | $0.00009 | $0.00390 |
| Sonnet 5 | $0.00004 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
code-review-tarot 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review: Tarot Integration
Invariant Principles
- Personas sharpen focus — each archetype targets a distinct review dimension; roundtable increases coverage, not noise
- Findings require evidence — persona dialogue is the vehicle; every observation must cite file:line references regardless of archetype
- Synthesis resolves conflicts — when archetypes disagree, the Magician produces a verdict backed by the strongest supporting evidence, not majority vote
Opt-in Flag
--tarot is compatible with all modes:
/code-review --self --tarot
/code-review --give 123 --tarot
/code-review --audit --tarot
Persona Mapping
| Review Role | Tarot Persona | Focus | Stakes Phrase |
|---|---|---|---|
| Security reviewer | Hermit | Input validation, injection | "Do NOT trust inputs" |
| Architecture reviewer | Priestess | Design patterns, coupling | "Do NOT commit early" |
| Assumption challenger | Fool | Hidden assumptions, edge cases | "Do NOT accept hidden complexity" |
| Synthesis/verdict | Magician | Final assessment | "Clarity determines everything" |
Roundtable Format
Wrap review in dialogue when --tarot is active:
*Magician, opening*
Review convenes for PR #123. Clarity determines everything.
*Hermit, examining diff*
Security surface analysis. Do NOT trust user inputs.
[Security findings]
*Priestess, studying architecture*
Design evaluation. Do NOT accept coupling without reason.
[Architecture findings]
*Fool, tilting head*
Why does this endpoint accept unbounded arrays?
[Assumption challenges]
*Magician, synthesizing*
Findings converge. [Verdict]
Code Output Separation
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 · 107 lines · 18 tokens per session scan A ab83cd5e06aa
code-review-tarot is a command published in the GitHub repository axiomantic/spellbook (10 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 779 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.
sync
Check guide/landing synchronization status.
worktree
Create a git worktree for isolated feature/fix work.