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-analyze)<a href="https://agentmods.dev/commands/axiomantic/spellbook/simplify-analyze"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/simplify-analyze.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.00013 | $0.03108 |
| Opus 5 | $0.00006 | $0.01554 |
| Sonnet 5 | $0.00003 | $0.00622 |
| Haiku 4.5 | $0.00001 | $0.00311 |
Grade A, and why
simplify-analyze 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 — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/simplify-analyze
Analyze code for cognitive complexity and identify simplification opportunities. Run standalone or as part of the /simplify workflow.
Invariant Principles
- Measure before transforming - Calculate cognitive complexity scores before proposing any changes
- Test coverage gates access - Functions without test coverage are excluded unless explicitly allowed
- Language-aware patterns - Apply language-specific idioms; generic patterns for unsupported languages
- Rank by impact and risk - High-impact, low-risk simplifications take priority over risky transformations
Usage
/simplify-analyze [target] [options]
Arguments
target: Optional. File path, directory path, or omit for branch changeset--staged: Only analyze staged changes--function=<name>: Target specific function (requires file path)--repo: Entire repository (prompts for confirmation)--base=<branch>: Override base branch for diff--allow-uncovered: Include functions with no test coverage--dry-run: Report only, no changes--no-control-flow: Skip guard clause/nesting transforms--no-boolean: Skip boolean simplifications--no-idioms: Skip language-specific modern idioms--no-dead-code: Skip dead code detection--min-complexity=<N>: Only simplify functions with score >= N (default: 5)--json: Output report as JSON--save-report=<path>: Save report to file
Step 1: Mode Selection and Scope Determination
1.1 Parse Command Arguments
Targeting modes (mutually exclusive):
- No target argument -> Branch changeset (default)
path/to/file.ext-> Explicit filepath/to/dir/-> Directory (recursive)--stagedflag -> Only staged changes--function=nameflag -> Specific function (requires file path)--repoflag -> Entire repository
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 · 395 lines · 13 tokens per session scan A 498b810138ab
simplify-analyze is a command published in the GitHub repository axiomantic/spellbook (10 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 3,108 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
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.
subagent-diagnose
Multi-agent failure-investigation orchestrator. Parallel to /subagent-implementation — same scratchpad + investigator + builder/surgeon + reviewer + FOLLOWUPS pattern — but starts from a failure, not a spec. Two modes share one loop: ci (failed CI run is the brief seed) and bug (freeform symptom paragraph is the brief…
quick-fix
Run the implement→review subagent loop without the planning phase — for straightforward fixes with a known cause and one obvious approach, regardless of how many files the change spreads across. Skips the spec gate, worktree gate, and finalize ceremony (implementation log, docs, signals) that /subagent-implementation…
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.
afr
Review feature - code review with fixes by a different agent (shortcut for feature-code-review).
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.