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/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/simplify-verify)<a href="https://agentmods.dev/commands/axiomantic/spellbook/simplify-verify"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/simplify-verify/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/axiomantic/spellbook/simplify-verify"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/simplify-verify.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.00014 | $0.00944 |
| Opus 5.5 | $0.00006 | $0.00378 |
| Sonnet 5.5 | $0.00003 | $0.00189 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
simplify-verify 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 1mo 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/simplify-verify
Run multi-gate verification on proposed simplifications before transformation. Part of the simplify-* command family; runs after /simplify-analyze, produces output for /simplify-transform.
Invariant Principles
- All gates must pass - Parse, type check, test run, and complexity delta; failure at any gate aborts the transformation
- Abort on failure, continue pipeline - Failed candidates are recorded and skipped; pipeline continues to next candidate
- Complexity must decrease - Transformations that do not reduce cognitive complexity are rejected
- Test coverage required - Untested functions are skipped unless explicitly allowed with
--allow-uncoveredand higher risk acknowledgment
Step 4: Verification Gate
4.1 Verification Pipeline
parse_check -> type_check -> test_run -> complexity_delta
| | | |
v v v v
FAIL? FAIL? FAIL? report
abort abort abort
4.2 Gate 1: Parse Check
Verify syntax validity:
# Python
python -m py_compile <file>
# TypeScript
tsc --noEmit <file>
# Nim
nim check <file>
# C/C++
gcc -fsyntax-only <file>
# or
clang -fsyntax-only <file>
If parse fails: Abort transformation. Mark as "verification failed - syntax error". Continue to next candidate.
4.3 Gate 2: Type Check
If language has a type system AND type annotations are present:
# Python (if type hints present)
mypy <file>
# TypeScript
tsc --noEmit <file>
# C/C++
# Covered by Gate 1 compile check
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.
- 1mo ago First seen · 131 lines · 14 tokens per session scan A 0f45126b306b
simplify-verify is a command published in the GitHub repository axiomantic/spellbook (11 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 944 once invoked, about $0.0001 per session on Opus 5.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
quick-fix
Implement→review subagent loop with no planning phase, for a fix whose cause is known and whose shape is obvious, however many files it touches. No spec, no worktree, no docs or signals at the end; one audit. Routes to /subagent-diagnose on an unknown cause and to /atomic-plan on an open approach or contract choice.
optimize
Suggest concrete performance improvements for the given file or directory.
verify-fix
Verify a fix actually works before claiming success - runs tests, checks live behavior, confirms fixes work from user perspective.
maintain
Run automated maintenance — seeker finds bugs from pod logs and raises GitHub issues, fixer picks them up and creates PRs. Can run as a one-shot or scheduled via /schedule.
test
Run the project test suite and triage any failures.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.