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/execute-plan)<a href="https://agentmods.dev/commands/axiomantic/spellbook/execute-plan"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/execute-plan/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/execute-plan"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/execute-plan.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.00023 | $0.00319 |
| Opus 5.5 | $0.00009 | $0.00128 |
| Sonnet 5.5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
execute-plan 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.
What it actually says
Execute Plan
Invoke executing-plans skill to execute implementation plans with verification and review gates.
Invariant Principles
- Plan Fidelity - Plans encode architect decisions. Deviation without approval corrupts the contract.
- Evidence Over Claims - Task completion requires verification output. Never mark complete without proof.
- Blocking Over Guessing - Uncertainty halts execution. Wrong guesses compound; asking costs one exchange.
Protocol
- Load
executing-plansskill - Follow skill instructions exactly - no interpretation, no improvisation
- Respect all review checkpoints and verification gates
- Stop on uncertainty; ask rather than guess
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 · 49 lines · 23 tokens per session scan A 4d9f434d63f4
execute-plan is a command published in the GitHub repository axiomantic/spellbook (11 stars, last pushed 6d ago), licensed MIT. It adds 23 tokens to every session and 319 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
report-issue-with-atomic
Open an issue against the atomic-claude repo itself (bugs/feature requests with the installed config, not the user's current project).
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.
asana-setup
Set up the Asana V2 MCP server connection (one-time OAuth app + fuxi mcp add).
save
Save current work state for next session. Creates/updates .planning/ files (CHECKPOINT.md, STATE.md, settings.json) so Heimdall resumes with full context. NOT a rewind — saves forward progress. Run before closing a session or at any milestone.
status
Show current Heimdall state — project phase, active agents, quality gates, conflicts.
align-context
Update all context files (task, spec, task-context, worklog) to reflect current state of work — fixes stale entries, fills missing knowledge, reports what changed.