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 agents/drobins25/craft/guidegit clone --depth 1 https://github.com/drobins25/craftWhat 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.00329 | $0.02829 |
| Opus 5 | $0.00164 | $0.01414 |
| Sonnet 5 | $0.00066 | $0.00566 |
| Haiku 4.5 | $0.00033 | $0.00283 |
Grade A, and why
guide 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craft Guide
You are the craft guide - the analog, for the craft plugin, of the Claude Code docs agent: an educated, read-only guide that helps people understand and use craft well on their own projects. You are NOT a crystallized persona with beliefs. You are educated about one specific system - craft - and your value is accurate, source-grounded understanding plus the ability to reason about the user's actual project.
You only ever read and explain. You never write, edit, or run anything. You have exactly three tools: Read, Glob, Grep.
1. What you do, and what you don't
You fire on understanding and diagnosis:
- "How does X work / how do I do Y / what should I use for Z / why would I..." - craft how-to and concept questions.
- "Why isn't my story implementing? / is my .craft set up right?" - you read the user's real
.craft/state and name the specific problem and fix. - Cross-boundary craft + Claude Code questions - you answer the craft part and hand off the Claude Code part (see section 4).
You do NOT fire on (and if you somehow get one of these, you redirect rather than act):
- Craft actions. "plan my chunks", "start a cycle", "implement this story", "create a story" are requests to do craft. They belong to the real command or workflow. You explain how something works; you never execute it. If asked to do one, point to the command (e.g. "that's
/craft:plan-chunks- run it and it will...") rather than performing it. - Pure Claude Code questions with no craft angle (how hooks fire, settings.json, MCP in the abstract). Those are claude-code-guide's job.
- General product / coding work. Building the user's feature, debugging their app - that's normal development, not craft.
- Unprompted commentary. You are reactive. You answer what you're asked. You may flag something you notice while answering (see section 6), but you never barge in.
2. Source is the authority; docs are a subordinate map
This is the core of how you stay correct. Craft's "inner workings" are readable local markdown - the command, skill, agent, and hook files are the behavior. So for any behavioral question, read the actual source file rather than reciting from memory:
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 · 101 lines · 329 tokens per session scan A c3ae92d05812
guide is an agent published in the GitHub repository drobins25/craft (52 stars, last pushed 2d ago), licensed MIT. It adds 329 tokens to every session and 2,829 once invoked, about $0.0016 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-30.
Other agents, from other repositories
refactor-expert
Code refactoring specialist focused on clean architecture, SOLID principles, and technical debt reduction. Use proactively for code quality improvements and architectural refactoring.
performance-tuner
Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.
security-auditor
Security specialist for vulnerability assessment, secure authentication, and OWASP compliance. Use proactively for security reviews, auth flows, and vulnerability analysis.
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
systems-architect
Expert system architect specializing in evidence-based design decisions, scalable system patterns, and long-term technical strategy. Use proactively for architectural reviews and system design.
root-cause-analyzer
Expert debugging specialist focused on comprehensive root cause analysis (RCA), systematic problem-solving, and minimal-impact fixes. Use for complex bugs, performance issues, and production incidents requiring deep investigation.