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 executing-plansgit 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/executing-plans)<a href="https://agentmods.dev/skills/axiomantic/spellbook/executing-plans"><img src="https://agentmods.dev/badge/skills/axiomantic/spellbook/executing-plans.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.00071 | $0.02850 |
| Opus 5 | $0.00036 | $0.01425 |
| Sonnet 5 | $0.00014 | $0.00570 |
| Haiku 4.5 | $0.00007 | $0.00285 |
Grade A, and why
executing-plans 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executing Plans
Announce: "Using executing-plans skill to implement this plan."
Invariant Principles
- Plan Fidelity: Follow plan steps exactly. Plans encode architect decisions; deviation creates drift. If plan seems wrong, ask - don't silently reinterpret.
- Evidence Over Claims: Every task completion requires verification output. Never mark complete without proof. "I ran the tests" without showing output is not evidence.
- Blocking Over Guessing: Uncertainty must halt execution. Wrong guesses compound; asking costs one exchange.
- Review Before Proceed: No task advances past unaddressed review findings. Spec compliance precedes code quality.
- Context Completeness: Subagents receive full task text, never file references. Fresh contexts lack your accumulated knowledge.
Working Directory Verification
Before executing any plan tasks, verify the working directory:
cd <WORKING_DIRECTORY> && pwd && git branch --show-current
If a working directory was specified in the dispatch context:
- Verify you are in the correct directory
- Verify the branch matches expectations
- ALL file paths must be absolute, rooted at the working directory
- ALL git commands must run from the working directory
- Do NOT create new branches. Work on the existing branch.
When dispatching implementer subagents, include the working directory verification in their prompts:
BEFORE ANY WORK:
1. cd <WORKING_DIRECTORY> && pwd && git branch --show-current
2. Verify the branch is <EXPECTED_BRANCH>
3. ALL file paths must be absolute, rooted at <WORKING_DIRECTORY>
4. ALL git commands must run from <WORKING_DIRECTORY>
5. Do NOT create new branches. Work on the existing branch.
What ships with it
3 files 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 · 321 lines · 71 tokens per session scan A 19b93ede9604
executing-plans is a skill published in the GitHub repository axiomantic/spellbook (10 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 2,850 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
atomic-review
Compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", or invokes /atomic-review. Auto-triggers when reviewing pull requests.
diff-to-graph
Turns a diff's touched functions and modules into graph nodes, reusing entities the graph already tracks, and links the change itself to each one with a modifies edge.
propose-graph-diff
Turns a proposed addition to a JSON-file graph into a minimal, reviewable diff, flagging any proposed edge that conflicts with a cross-reference already on file, and never writing directly to the shared graph file itself.
type-design-analyzer
Analyzes newly-added or significantly-modified types in a pull request for invariant strength, encapsulation, and enforcement. Produces 1-10 ratings on encapsulation/expression/usefulness/enforcement with concrete improvement suggestions. Use when reviewing PRs that introduce or substantially change types, classes…
silent-failure-hunter
Audits error-handling code in a pull request for silent failures, broad catch blocks, unjustified fallbacks, and unactionable error messages. Surfaces hidden failures users would otherwise hit in production. Use when reviewing PRs that add or modify try/catch, error callbacks, or fallback logic.
comment-analyzer
Audits code comments added or changed by a pull request for factual accuracy against the code, long-term maintenance value, and misleading content. Recommends specific edits, additions, or removals. Use when reviewing PRs that include new or modified comments, docstrings, or inline documentation.