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 skills add axiomantic/spellbook --skill requesting-code-reviewgit 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/skills/axiomantic/spellbook/requesting-code-review)<a href="https://agentmods.dev/skills/axiomantic/spellbook/requesting-code-review"><img src="https://agentmods.dev/badge/skills/axiomantic/spellbook/requesting-code-review.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.1 | $0.00077 | $0.00942 |
| Opus 5 | $0.00039 | $0.00471 |
| Sonnet 5 | $0.00015 | $0.00188 |
| Haiku 4.5 | $0.00008 | $0.00094 |
Grade A, and why
requesting-code-review 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 3d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requesting Code Review
Invariant Principles
- Phase gates are blocking - Never proceed to next phase without meeting exit criteria
- Evidence over opinion - Every finding must cite specific code location and behavior
- Critical findings are non-negotiable - No Critical finding may be deferred or ignored
- SHA persistence - Always use reviewed_sha from manifest, never current HEAD
- Traceable artifacts - Each phase produces artifacts for resume and audit capability
Phase-Gated Workflow
Reference: patterns/code-review-formats.md for output schemas.
Phases 1-2: Planning + Context
Determine git range, list changed files, identify plan/spec, estimate complexity. Assemble reviewer context bundle: plan excerpts, related code, prior findings.
Execute: /request-review-plan
Outputs: Review scope definition, reviewer context bundle
Self-Check: Git range defined, file list confirmed, context bundle ready for dispatch.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 99 lines · 77 tokens per session scan A 35afdb6dd36e
requesting-code-review is a skill published in the GitHub repository axiomantic/spellbook (10 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 942 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
atomic-git-discipline
Compressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, 120 words max. Use when user says "write a commit", "commit message", "generate…
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
plate
Turn finished local work into a commit, an ordinary pull request, or a pull request stack. Use this skill to commit changes or to publish a branch. Use it to open or update a pull request. Use it to create, sync, restack, or submit a pull request stack. You can also run /plate. This skill owns all staging, commits…
phase-commit
Create one local commit for a completed, validated, and reviewed unit of work. Use only when the user explicitly requests a commit without pushing or other delivery actions.
create-commit
Create a git commit whose message records why the change exists, not just what changed. Stages only the files that belong to the change, matches the repo's existing commit style, and shows the message and staged files for user approval before committing. Use when asked to commit work or write a commit message.…