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/testgit 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.00008 | $0.01732 |
| Opus 5 | $0.00004 | $0.00866 |
| Sonnet 5 | $0.00002 | $0.00346 |
| Haiku 4.5 | $0.00001 | $0.00173 |
Grade A, and why
test 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/craft:test - Unified Test Runner
Run, debug, measure coverage, and watch tests with a single command. Replaces the
old test:run, test:coverage, test:debug, and test:watch commands.
Quick Start
/craft:test # Run all tests (default mode)
/craft:test unit # Run only unit tests
/craft:test e2e # Run only e2e tests
/craft:test hub # Run only hub domain tests
/craft:test --coverage # Run with coverage report
/craft:test --watch # Watch mode
/craft:test debug # Debug mode (verbose traces)
/craft:test unit --filter="auth" # Unit tests matching "auth"
/craft:test --dry-run # Preview execution plan
Category Filtering
Filter tests by tier or domain using pytest markers defined in pyproject.toml:
Tiers (mutually exclusive)
| Tier | Marker | Count | Speed |
|---|---|---|---|
unit |
@pytest.mark.unit |
~489 | < 2s |
integration |
@pytest.mark.integration |
~568 | < 30s |
e2e |
@pytest.mark.e2e |
~333 | < 60s |
smoke |
@pytest.mark.smoke |
subset | < 30s |
Domains (combinable with tiers)
| Domain | Tests For |
|---|---|
hub |
Hub discovery, display, layers |
claude_md |
CLAUDE.md sync, audit, fix |
branch_guard |
Branch protection hooks |
orchestrator |
Orchestrator workflows |
commands |
Command parsing, discovery |
structure |
Plugin structure validation |
docs |
Documentation link checking |
badge |
Badge detection and syncing |
brainstorm |
Brainstorm context |
release |
Release pipeline |
marketplace |
Marketplace distribution |
formatting |
Box-drawing, ANSI |
dependency |
Dependency management |
site |
Site publishing |
Combining Filters
/craft:test "unit and hub" # Unit tests for hub only
/craft:test "integration and not slow" # Fast integration tests
/craft:test "e2e and branch_guard" # Branch guard e2e only
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 · 237 lines · 8 tokens per session scan A 6aa5cad66ec7
test is a command published in the GitHub repository Data-Wise/craft (4 stars, last pushed 16d ago), licensed MIT. It adds 8 tokens to every session and 1,732 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.