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/nWave-ai/nWaveWrote 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/nwave-ai/nwave/distill)<a href="https://agentmods.dev/commands/nwave-ai/nwave/distill"><img src="https://agentmods.dev/badge/commands/nwave-ai/nwave/distill/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/nwave-ai/nwave/distill"><img src="https://agentmods.dev/badge/commands/nwave-ai/nwave/distill.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.00026 | $0.04997 |
| Opus 5.5 | $0.00010 | $0.01999 |
| Sonnet 5.5 | $0.00005 | $0.00999 |
| Haiku 4.5 | $0.00003 | $0.00500 |
Grade A, and why
distill 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 — 407 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NW-DISTILL: Acceptance Test Creation and Business Validation
Wave: DISTILL (wave 5 of 6) | Agent: Quinn (nw-acceptance-designer)
Overview
Orchestrate acceptance test creation from prior wave artifacts, then gate the result through parallel reviews before handoff to DELIVER. You (main Claude instance) are the orchestrator. You dispatch agents and enforce gates.
The AT-completeness gate, MAX-PBT mandate, and Mandate-12 step-reuse metric are advisory.
REVIEW GATE SUMMARY (read this first)
After the acceptance designer produces scenarios, you MUST dispatch 4 parallel reviewers if scenario count exceeds 3 (Eclipse + Architect + Forge + Sentinel). Sentinel (@nw-acceptance-designer-reviewer) is the structural-correctness reviewer — it ALWAYS dispatches even on fast-path or under rigor.reviewer_model: "skip" (which only skips scale-sensitive cost-driven reviewers). This is the single most important orchestration step in DISTILL. The procedure is: dispatch designer -> count scenarios -> dispatch 4 reviewers in parallel -> AND-gate results -> handoff. Details in Phase 3 below.
Phase 1: Decisions and Context
Interactive Decision Points
Decision 1: Feature Scope
Question: What is the scope of this feature? Options:
- Core feature -- primary application functionality
- Extension -- modular add-on or integration
- Bug fix -- regression tests for a known defect
Decision 2: Test Framework
Question: Which test framework to use? Options:
- pytest-bdd -- Python BDD framework
- Cucumber -- Ruby/JS BDD framework
- SpecFlow -- .NET BDD framework
- Custom -- user provides details
Decision 3: Integration Approach
Question: How should integration tests connect to services? Options:
- Real services -- test against actual running services
- Test containers -- ephemeral containers for dependencies
- Mocks for external only -- real internal, mocked external services
Decision 4: Infrastructure Testing
Question: Should acceptance tests cover infrastructure concerns? Options:
- Yes -- include CI/CD validation, deployment smoke tests
- No -- functional acceptance tests 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 · 407 lines · 26 tokens per session scan A c6e90fa620ef
distill is a command published in the GitHub repository nWave-ai/nWave (621 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 4,997 once invoked, about $0.0001 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-09-06.
Other commands, from other repositories
implement
E2E-first Test driven development — unit tests written last.
health-check
Perform a comprehensive, read-only end-to-end review of any portfolio app across three layers — Frontend (E2E), Database integrity, and Audit Log & User Activity — and produce a structured, observations-only report. Optionally, on explicit opt-in, generate (never apply) the infrastructure provisions needed so future…
gba-test
$ARGUMENTS: test mode — game profile defines available modes (e.g., smoke, gameplay, save, stress, full, ai, battle, nav, custom ).
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
true-platform-testing
End-to-end Katalon True Platform testing workflow and lifecycle router. Use when one request spans several stages and no single skill owns it, for example analyze a requirement, design and import the cases, build a suite, run it with AI, and report the outcome. Also use to route any testing request across the 7-stage…
build-from-figma
You are the master orchestrator for converting a Figma design into a fully working, tested React application. You receive a Figma URL and guide the entire process through 9 phases, using specialized skills and agents.