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.
git clone --depth 1 https://github.com/Data-Wise/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/data-wise/craft/test)<a href="https://agentmods.dev/commands/data-wise/craft/test"><img src="https://agentmods.dev/badge/commands/data-wise/craft/test/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/data-wise/craft/test"><img src="https://agentmods.dev/badge/commands/data-wise/craft/test.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00008 | $0.01732 |
| Opus 5.5 | $0.00003 | $0.00693 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago 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 7d ago), licensed MIT. It adds 8 tokens to every session and 1,732 once invoked, about $0.0000 per session on Opus 5.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
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
judge-ci-red
Load when: loom-daemon forge wait-checks printed LOOM-CHECKS-RED, or post-verdict.sh … approved exited 6, and a CI-failing verdict is next.
write-test-plan
Generate or update change test plan.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.
ci-setup
Setup CI pipeline from scratch. Creates GitHub Actions or GitLab CI configuration with lint, test, build, and deploy stages.
ship
Before merging or deploying, run ALL of the following checks. Every gate must pass.