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/data-wise/craft/overviewgit clone --depth 1 https://github.com/Data-Wise/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.00000 | $0.02245 |
| Opus 5 | $0.00000 | $0.01123 |
| Sonnet 5 | $0.00000 | $0.00449 |
| Haiku 4.5 | $0.00000 | $0.00225 |
Grade A, and why
overview scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Distribution** (4): Marketplace, Homebrew (formula+cask), PyPI, curl installers — [Learn more →](dist.md) How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commands Overview
TL;DR (30 seconds)
- What: 48 commands organized into 17 categories covering the full development lifecycle
- Why: One plugin handles your entire development workflow from docs to deployment
- How: Use
/craft:hubto discover all commands by category- Next: Start with
/craft:dofor AI-powered task routing or/craft:checkfor pre-flight validation
Craft provides 48 commands for full-stack development workflows.
Command Routing
flowchart TD
User["User Task"] --> Do["/craft:do"]
Do --> |"docs/writing"| Docs["📚 Docs (21)"]
Do --> |"code/debug"| Code["💻 Code (15)"]
Do --> |"site/deploy"| Site["🌐 Site (16)"]
Do --> |"git/branch"| Git["🔀 Git (13)"]
Do --> |"test/coverage"| Test["🧪 Test (3)"]
Do --> |"ci/deploy"| CI["⚙️ CI (4)"]
Do --> |"architecture"| Arch["🏗️ Arch (4)"]
Do --> |"distribute"| Dist["📦 Dist (4)"]
Do --> |"plan/sprint"| Plan["📋 Plan (3)"]
Do --> |"workflow"| WF["🔄 Workflow (13)"]
Do --> |"complex task"| Orch["/craft:orch (3)"]
Hub["/craft:hub"] -.-> |"discover"| Do
Check["/craft:check (2)"] -.-> |"validate"| Do
Smart["/craft:smart-help"] -.-> |"guide"| Do
style Do fill:#4a9eff,color:#fff
style Hub fill:#6c757d,color:#fff
style Check fill:#6c757d,color:#fff
style Smart fill:#6c757d,color:#fff
Command Categories
🎯 Smart and Discovery (8)
Universal commands with AI-powered routing:
/craft:do <task>— Universal task router/craft:check [--for]— Pre-flight checks/craft:orch <task> [mode]— Enhanced orchestrator (+plan,resume)/craft:hub— Command discovery/craft:smart-help— Context-aware help
📚 Documentation Commands (21)
Smart documentation generation and validation:
- Super Commands:
update,sync,check,check-links - CLAUDE.md:
init,sync,edit - Specialized:
api,changelog,guide,demo,mermaid,website
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.
- yesterday First seen · 275 lines · 0 tokens per session scan A d53413d7c97c
overview is a command published in the GitHub repository Data-Wise/craft (4 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,245 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
readme-audit
Audit a README's reading flow by treating it as a conversion funnel. Every section is evaluated against a target reader and a terminal action. Produces a structured audit blueprint that feeds directly into /readme-restructure.
readme-restructure
Execute a /readme-audit blueprint. Rewrites the README to the evaluator → conversion → links structure and creates linked docs by extracting and reorganising existing content.
build-fix
Fix build and type failures with minimal diffs.
checkpoint
Record a verified checkpoint before the next phase.
doctor
Check the install surface for missing files and invalid manifests.
feature-dev
Drive a feature from plan to implementation to review.