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/feature-config)<a href="https://agentmods.dev/commands/axiomantic/spellbook/feature-config"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/feature-config/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/feature-config"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/feature-config.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.00017 | $0.10748 |
| Opus 5 | $0.00009 | $0.05374 |
| Sonnet 5 | $0.00003 | $0.02150 |
| Haiku 4.5 | $0.00002 | $0.01075 |
Grade A, and why
feature-config 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 5d 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 — 864 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Configuration (Phase 0)
Invariant Principles
- Configuration before execution - Collect all preferences upfront; never proceed with incomplete configuration.
- Escape hatch detection - Existing documents bypass phases they cover; detect before asking redundant questions.
- Motivation drives design - Understanding WHY shapes every subsequent decision; never skip motivation clarification.
- Continuation awareness - Detect and honor prior session state; artifacts indicate progress, not fresh starts.
- Ceremony is chosen once, then locked - develop assesses and recommends; the operator decides; the decision is written to the ledger and is immutable for the run. Escalation stays legal; de-escalation never becomes legal.
0.5 Continuation Detection
Continuation Signals (any of):
- User prompt contains: "continue", "resume", "pick up", "where we left off", "compacted"
- MCP
<system-reminder>contains**Skill Phase:**with develop phase - MCP
<system-reminder>contains**Active Skill:** develop - Artifacts exist in expected locations for current project
If NO continuation signals: Proceed to 0.1.
If continuation signals detected:
Step 1: Parse Recovery Context
Extract from <system-reminder> (if present):
active_skill,skill_phase(e.g., "Phase 2: Design"),todos,exact_position
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.
- 5d ago First seen · 864 lines · 17 tokens per session scan A 7e825f119e11
feature-config is a command published in the GitHub repository axiomantic/spellbook (10 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 10,748 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
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.
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.
beads-loop
Execute beads iteratively until all tasks complete.
beads-swarm
Execute beads with parallel agent swarm (dependency-aware).