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/design-assessment)<a href="https://agentmods.dev/commands/axiomantic/spellbook/design-assessment"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/design-assessment.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.00043 | $0.03229 |
| Opus 5 | $0.00022 | $0.01614 |
| Sonnet 5 | $0.00009 | $0.00646 |
| Haiku 4.5 | $0.00004 | $0.00323 |
Grade A, and why
design-assessment 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 8d 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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MISSION
Generate complete assessment frameworks for evaluative skills and commands. Auto-detects target type, selects appropriate dimensions, and outputs a unified markdown framework with all sections needed for evaluation.
Invariant Principles
- Target type determines dimensions: Each target type has default dimensions optimized for that evaluation context
- Severity vocabulary is fixed: CRITICAL/HIGH/MEDIUM/LOW/NIT matches existing spellbook skills
- Confidence requires evidence: Every confidence level maps to specific evidence requirements
- Blocking dimensions gate verdicts: Blocking dimension failures prevent approval regardless of other scores
- Mode determines interaction: Autonomous proceeds without questions; interactive presents dimension menu
Inputs
| Input | Source | Required | Description |
|---|---|---|---|
target_description |
User message | Yes | What is being assessed (e.g., "code review skill", "design doc validator") |
target_type |
User message or auto-detect | No | Override: code, document, api, test, claim, artifact, readiness |
mode |
User message | No | autonomous (default) or interactive |
existing_file |
User message | No | Path to skill/command being updated - read for context |
Phase 1: Detect Target Type
Detection patterns (first match wins):
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.
- 8d ago First seen · 331 lines · 43 tokens per session scan A 76b6f9e727bc
design-assessment is a command published in the GitHub repository axiomantic/spellbook (10 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 3,229 once invoked, about $0.0002 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-08-31.
Other commands, from other repositories
subagent-implementation
Orchestrate implement→review subagent loop until task complete. Reads the approved spec, writes a thin brief to .claude/.scratchpad/, dispatches fresh-context subagents, loops until reviewer signs off, commits per green iteration, then updates repo docs.
documentation
Bootstrap and maintain project documentation surfaces. Two modes: bootstrap (discover doc files, index them in CLAUDE.md) and authoring (scan for unindexed docs, match diff against indexed surfaces, walk stale/incomplete/missing items with Yes/Later/Remind/Skip).
watch-ci
Spawn a background Haiku-backed subagent to watch CI for the current branch (or specified target). Provider-agnostic — the subagent inspects project signals to identify the CI system (GitHub Actions, GitLab CI, CircleCI, etc.) and picks the right CLI. Returns immediately; reports back when CI reaches a terminal state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
integrate
Analyze and enhance AI artifacts to leverage Subcog memory effectively.
add-command
Add a new slash command to the current plugin.