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/create-issue)<a href="https://agentmods.dev/commands/axiomantic/spellbook/create-issue"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/create-issue/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/create-issue"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/create-issue.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.00011 | $0.04590 |
| Opus 5.5 | $0.00004 | $0.01836 |
| Sonnet 5.5 | $0.00002 | $0.00918 |
| Haiku 4.5 | $0.00001 | $0.00459 |
Grade A, and why
create-issue 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 — 528 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You MUST:
- NEVER create an issue without explicit user approval via AskUserQuestion
- NEVER use
--templateflag withgh issue create - NEVER fabricate Jira ticket numbers
- Always attempt template discovery before falling back to blank issue
- Always use
--body-filefor issue body (never inline--bodyfor non-trivial content)
This is NOT optional. This is NOT negotiable.
Invariant Principles
- User Approval Required: NEVER create an issue without explicit AskUserQuestion approval.
- Template Discovery First: Always attempt all discovery tiers; run Tier 2 even if Tier 1 yields results (Tier 1 returns markdown-only; Tier 2 catches YAML forms).
- Safe CLI Patterns: Use
--body-filewith temp files. Never--template. Never unquoted heredocs. - No Fabricated Tickets: Omit
[ODY-XXXX]prefix entirely if no Jira ticket is evident. - Respect Repository Config: Honor
blank_issues_enabled: falseand required field validations.
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 · 528 lines · 11 tokens per session scan A 69097e893b02
create-issue is a command published in the GitHub repository axiomantic/spellbook (10 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 4,590 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
prepare-release
Prepare a version release — follows project release config in .aicontext/release.md, runs first-time setup if config is missing.
run-task
Run pending steps, then aftertask finalization; does not close the task.
finish-task
Deprecated alias for close-task.
worktree
Create a git worktree for isolated feature/fix work.
resume-project
Run resume-project now — Now / Blocked / Next. Not a cheat sheet.
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.