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/drobins25/craft/craft-statusgit clone --depth 1 https://github.com/drobins25/craftWrote 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/drobins25/craft/craft-status)<a href="https://agentmods.dev/commands/drobins25/craft/craft-status"><img src="https://agentmods.dev/badge/commands/drobins25/craft/craft-status.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 | $0.00018 | $0.02478 |
| Opus 5 | $0.00009 | $0.01239 |
| Sonnet 5 | $0.00004 | $0.00496 |
| Haiku 4.5 | $0.00002 | $0.00248 |
Grade A, and why
status 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craft Status
Display a comprehensive view of current Craft state.
Dashboard Format
┌─────────────────────────────────────────────────────────────┐
│ CRAFT $X.XX │
├─────────────────────────────────────────────────────────────┤
│ │
│ ● Cycle [N]: [Name] [status] │
│ ├── ✓ [Story 1] complete │
│ ├── ◐ [Story 2] chunk X/Y ███░░ │
│ └── ○ [Story 3] ready │
│ │
│ ○ Cycle [N+1]: [Name] [status] │
│ └── X stories planned │
│ │
├─────────────────────────────────────────────────────────────┤
│ Backlog: X stories │
│ ├── [story-name] (priority) │
│ ├── [story-name] │
│ └── +N more │
└─────────────────────────────────────────────────────────────┘
Status Indicators
| Symbol | Meaning |
|---|---|
○ |
Ready/Pending |
◐ |
In Progress |
✓ |
Complete |
⚠ |
Blocked |
✗ |
Failed |
Planning Section
If .craft/planning/ exists, show a planning summary between the cycle dashboard and the backlog:
├─────────────────────────────────────────────────────────────┤
│ Planning updated 2 days ago │
│ ► customer-modernization (3 concepts, 1 planned) │
│ ├── profile-tab complete │
│ ├── cdb-mapping planned │
│ └── invoice-email open │
│ ○ permissions-cleanup open │
│ ○ user-preferences open │
│ ? 4 open questions across 3 concepts │
├─────────────────────────────────────────────────────────────┤
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 · 186 lines · 18 tokens per session scan A 398042135836
status is a command published in the GitHub repository drobins25/craft (53 stars, last pushed 6d ago), licensed MIT. It adds 18 tokens to every session and 2,478 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-30.
Other commands, from other repositories
claudehut-learning-report
Show the ClaudeHut learning scoreboard — measured memory health (store size, reinforcement, effectiveness/recurrence, quality) so you can tell whether the agent is actually getting smarter across sessions. One-shot, read-only.
orchestrate
This tool coordinates Claude Code's actions. It does NOT write code or create content.
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
performance-bottlenecks
Identify and resolve performance bottlenecks in your development workflow.