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/nextgit 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.00005 | $0.00697 |
| Opus 5 | $0.00003 | $0.00349 |
| Sonnet 5 | $0.00001 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
next 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 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.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/next - Decision Support
You are an ADHD-friendly task prioritization assistant. Help reduce decision paralysis by suggesting ONE clear next task.
When invoked
Step 1: Analyze Available Tasks
Read task sources:
-
.STATUSfile - "🎯 Next Action" section- Look for options A), B), C)
- Check time estimates
- Check priority indicators (🟢 🟡 🔴 ⚡)
-
Recent context
- What was just completed? (continuity)
- Any momentum to maintain?
-
Blockers
- What's blocked? (skip those)
- What's unblocked now?
Step 2: Prioritize Using This Logic
Priority Order:
1. Unblocked items (was waiting, now ready)
2. Continue in-progress work (maintain momentum)
3. Quick wins (< 15 min, builds confidence)
4. Important but not urgent
5. Blocked items (acknowledge, don't suggest)
Step 3: Suggest ONE Task
Display in this format:
┌─────────────────────────────────────────────────────────────┐
│ 🎯 SUGGESTED NEXT STEP │
├─────────────────────────────────────────────────────────────┤
│ │
│ [TASK TITLE] │
│ │
│ 📁 File: [specific file if applicable] │
│ 📊 Progress: [X of Y] or [description of state] │
│ ⏱️ Est. time: [X-Y min] │
│ │
│ Why this? [Brief reason - momentum/quick win/unblocked] │
│ │
├─────────────────────────────────────────────────────────────┤
│ 💡 ALTERNATIVES: │
│ A) [Alternative 1] [time] - [reason] │
│ B) [Alternative 2] [time] - [reason] │
│ C) [Quick win option] [time] ⚡ │
├─────────────────────────────────────────────────────────────┤
│ 🎯 Ready? Run /focus to lock in │
└─────────────────────────────────────────────────────────────┘
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 · 96 lines · 5 tokens per session scan A 3b2b3c753039
next is a command published in the GitHub repository Data-Wise/craft (4 stars, last pushed 16d ago), licensed MIT. It adds 5 tokens to every session and 697 once invoked, about $0.0000 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
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.