Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/axiomantic/spellbooknpx agentmods add commands/axiomantic/spellbook/pr-distillWrote 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/pr-distill)<a href="https://agentmods.dev/commands/axiomantic/spellbook/pr-distill"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/pr-distill.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.00017 | $0.00713 |
| Opus 5 | $0.00009 | $0.00357 |
| Sonnet 5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
pr-distill 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Distill
Invariant Principles
- Heuristics First: Run heuristic pattern matching before AI analysis. Heuristics are fast and deterministic.
- Confidence Requires Evidence: Never mark a change as "safe to skip" without pattern match or AI justification.
- Surface Uncertainty: Low-confidence cases → categorize as "uncertain". Humans decide ambiguous cases.
- Preserve Context: Include enough diff context for reviewers to understand changes without switching to the PR.
Execution
Phase 1: Fetch, Parse, Match
node lib/distilling-prs/index.js <pr-identifier>
Phase 2: Complete Analysis
node lib/distilling-prs/index.js --continue <pr-identifier> <ai-response-file>
Usage
/distilling-prs <pr-number-or-url>
Examples
/distilling-prs 123
/distilling-prs https://github.com/owner/repo/pull/456
Output
Report path: ~/.local/spellbook/docs/<project-encoded>/pr-reviews/pr-<number>-distill.md
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 · 92 lines · 17 tokens per session scan A fcdf15a2df30
pr-distill is a command published in the GitHub repository axiomantic/spellbook (10 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 713 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-09-03.
Other commands, from other repositories
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
dream
Overnight autoresearch + maintainer sweep that surfaces a MORNING REPORT — suggested changes, issues raised with fixes, and kept improvements. Shadow-first; never auto-pushes. Runs on-demand or scheduled for off-hours.
code-quality-plan-creator
LSP-powered architectural code quality analysis - works with any executor (loop or swarm).
mr-description-creator
Generate and apply MR/PR description directly via gh or glab CLI (project).
follow-up
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
unforgit-curate
Review and improve Unforgit memory quality.