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/codegit 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.00802 |
| Opus 5 | $0.00000 | $0.00401 |
| Sonnet 5 | $0.00000 | $0.00160 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
code 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code & Testing Commands
Development workflow tools with mode support - 48 commands.
When to Use What
| Scenario | Command | Why |
|---|---|---|
| Quick style check before commit | /craft:code:lint |
Fast default mode (< 10s) |
| Full pre-flight validation | /craft:check |
Runs lint + tests + links together |
| Deep debugging with traces | /craft:code:lint debug |
Verbose output with fix suggestions |
| Run unit tests | /craft:test |
Auto-detects framework (pytest, jest) |
| Test CLI tool behavior | /craft:test |
Validates stdin/stdout/exit codes |
| Run CI checks locally | /craft:ci:local |
Full CI pipeline without pushing |
| Check for vulnerabilities | /craft:code:deps-audit |
Security-focused dependency scan |
| Pre-release validation | /craft:code:lint release |
Comprehensive + types + security |
Common confusion:
- lint vs check —
lintchecks code style only;checkvalidates docs, links, and counts too - test vs code:test-gen —
testruns tests;code:test-gengenerates test suites (renamed fromtest:genin v4) - lint vs ci-local —
lintchecks one thing fast;ci-localruns the full CI pipeline locally
Linting & Code Quality
/craft:code:lint
/craft:code:lint # default mode
/craft:code:lint debug # Verbose with suggestions
/craft:code:lint optimize # Fast parallel linting
Testing
/craft:test
/craft:test # default mode
/craft:test debug # Verbose test output
/craft:test release # Full suite with coverage
CI/CD Commands
/craft:ci:fix
Auto-fix common CI/CD issues (linting, formatting, missing files).
/craft:ci:local
Run CI checks locally before pushing.
Dependencies
/craft:code:deps-audit
Security audit of dependencies with vulnerability reports.
/craft:code:deps-check
Check for outdated dependencies and breaking changes.
Documentation Integration
/craft:code:docs-check
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 · 114 lines · 0 tokens per session scan A 1719f13e39f9
code 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 802 tokens. 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.