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 agents/nwave-ai/nwave/nw-test-optimizergit clone --depth 1 https://github.com/nWave-ai/nWaveWhat 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.00227 |
| Opus 5 | $0.00000 | $0.00113 |
| Sonnet 5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
nw-test-optimizer 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 3d 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.
What it actually says
nw-test-optimizer
Use to minimize test count while preserving coverage. Invoke after a feature lands, when a suite feels slow or noisy, on a scheduled audit, or whenever the maintainer suspects overtesting. Detects byte-identical pairs, parametrize-inflation, language-guarantee tests, AST-shape tests, and migration-collapse opportunities. Never modifies production code.
Wave: Other Model: sonnet Max turns: 40 Tools: Read, Edit, Write, Bash, Glob, Grep, Task
Commands
Skills
- nw-tdd-methodology — Deep knowledge for Outside-In TDD - double-loop architecture, ATDD integration, port-to-port testing, walking skeletons, and test doubles policy
- nw-test-optimization — Methodology for minimizing test count while maximizing behavioral coverage - behavior definition, anti-pattern catalog, consolidation patterns, stopping criterion, coverage-preserving validation
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.
- 3d ago First seen · 18 lines · 0 tokens per session scan A b686d3d56440
nw-test-optimizer is an agent published in the GitHub repository nWave-ai/nWave (602 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 227 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-30.
Other agents, from other repositories
product-manager
Conducts grill-me interview to deeply understand the feature, then decomposes it into tracer bullet slices and emits scope.json. Runs as the sole Plan phase agent. Use for /sdlc-plan to kick off any feature.
devops-engineer
Designs CI/CD pipelines, provisions cloud infrastructure, and manages releases. Absorbed cloud-engineer and release-manager responsibilities. Runs as the sole Ship phase agent. Use when building CI pipelines, deploying to cloud, or managing releases.
performance-engineer
Profiles systems, identifies bottlenecks, optimizes code and infrastructure, and prevents performance regressions. Uses flame graphs, benchmarking, and data-driven analysis. Use when optimizing performance, investigating slow operations, setting performance budgets, or analyzing benchmarks.
technical-writer
Writes API documentation, SDK guides, tutorials, developer guides, and external communication. Makes technical concepts accessible to diverse audiences. Maintains docs-as-code philosophy with examples and runnable code. Use when creating API docs, writing developer guides, documenting SDKs, or creating tutorials.
ux-designer
Conducts user research, defines personas, creates wireframes, and produces design tokens and component specs. Runs once at the start of the Build phase when hasui is true. Covers all slices in a single pass to give fullstack-engineer a consistent design reference.
qa-engineer
Writes cross-slice E2E tests covering flows that span multiple slices. Runs once after all feature slices complete in the Build phase. Reads implementation-log.md to understand the full shape of what was built. Flags which slices caused any E2E failures for targeted retry.