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 agentmods add commands/redhuntlabs/wizard/build-spellgit clone --depth 1 https://github.com/redhuntlabs/wizardWhat 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 | $0.00015 | $0.00338 |
| Opus 5 | $0.00008 | $0.00169 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
build-spell 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 2d 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
/build-spell
Invoke the building-a-spell skill to start an interview that captures a new spell.
The interview will:
- Extract context from your trigger phrase (skip questions you already answered)
- Pick the right depth (Express, Standard, Deep) for your skill complexity
- Match against known workflow shapes if applicable
- Route to the correct kind-specific builder (content / workflow / discipline / subagent)
- Run try-it (non-skippable — Iron Law)
- Save to your
WIZARD_HOME
If you ask for multiple spells in one go, the meta-builder will complete each one end-to-end before starting the next (Batch Iron Law).
Building from an existing transcript
If you have a transcript of a session that worked (from any AI tool, a meeting, or a Loom transcript), skip the interview and infer the skill from it:
/build-spell --from-transcript ./session.md
The transcript is parsed by inferring-a-spell-from-examples, which produces a draft you can approve, refine in chat, or fall back to the regular interview from. Try-it (Iron Law) still runs.
For capturing the current chat session instead, use /capture-this-chat.
Usage
/build-spell
/build-spell I want to capture how I write status updates
/build-spell a workflow for when I review a job candidate's portfolio
/build-spell --from-transcript ./yesterday-session.md
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.
- 2d ago First seen · 41 lines · 15 tokens per session scan A 1909ce6b2168
build-spell is a command published in the GitHub repository redhuntlabs/wizard (9 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 338 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-08-31.
Other commands, from other repositories
generate-skill
从 GitHub URL 自动生成技能并发布。使用方法：/generate-skill.
fest-commit
Commit changes with festival traceability metadata.
camp-init
Initialize a new campaign workspace.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
fest-validate
Validate festival structure and find issues.
fest-list
List all festivals with their status and completion percentage.