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 skills/nwave-ai/nwave/nw-executenpx skills add nWave-ai/nWave --skill nw-executegit 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/skills/nwave-ai/nwave/nw-execute)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-execute"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-execute.svg" alt="Measured on agentmods" 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 | $0.00056 | $0.02943 |
| Opus 5 | $0.00028 | $0.01471 |
| Sonnet 5 | $0.00011 | $0.00589 |
| Haiku 4.5 | $0.00006 | $0.00294 |
Grade C, and why
nw-execute scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Build system injects mandatory phases from step-tdd-cycle-schema.json --> How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NW-EXECUTE: Atomic Task Execution
Wave: EXECUTION_WAVE | Agent: Dispatched agent (specified by caller)
Overview
Dispatch one unit of DELIVER work to an agent: a single roadmap step. /nw-execute extracts the step from roadmap.json and dispatches it for the 3-phase TDD canon; the agent appends phase events to execution-log.json.
Syntax
/nw-execute @{agent} "{feature-id}" "{step-id}"
Context Files Required
docs/feature/{feature-id}/deliver/roadmap.json— Orchestrator reads once, extracts step contextdocs/feature/{feature-id}/deliver/execution-log.json— Agent appends only (never reads)
Rigor Profile Integration
Before dispatching the agent, read rigor config from .nwave/des-config.json (key: rigor). If absent, use standard defaults.
agent_model: Pass asmodelparameter to Agent tool. If"inherit", omitmodel(inherits from session).tdd_phases: Modify the TDD_PHASES section in the DES template to match the configured phases. The 3-phase canon (ADR-025) is[RED, GREEN, COMMIT]; the lean variant is[RED, GREEN]. Legacy 5-phase contract ([PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, COMMIT]) and its lean variant ([RED_UNIT, GREEN]) remain supported for audit-log replay of pre-2026-05-07 commits. Remove omitted phases' instructions from the template.refactor_pass: Iffalse, skip COMMIT phase refactoring instructions.
Dispatcher Workflow
- Parse Parameters — Extract agent name, feature ID, and step ID from invocation. Gate: all three parameters present and non-empty.
- Load Rigor Profile — Read
.nwave/des-config.jsonkeyrigor(default: standard if absent). Gate: config loaded or default applied. - Validate Context Files — Confirm
roadmap.jsonandexecution-log.jsonexist underdocs/feature/{feature-id}/deliver/. Gate: both files present; report path-not-found if missing. - Extract Step Context — Grep roadmap for
step_id: "{step-id}"with ~50 lines context. Gate: step found; report available step IDs if missing. - Invoke Agent — Call Agent tool with DES template below, applying rigor model and phases from step 2. Gate: Agent tool called, not executed inline.
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 · 231 lines · 56 tokens per session scan C e44571a7ce81
nw-execute is a skill published in the GitHub repository nWave-ai/nWave (604 stars, last pushed 5d ago), licensed MIT. It adds 56 tokens to every session and 2,943 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
agent-implementer-sparc-coder
Agent skill for implementer-sparc-coder - invoke with $agent-implementer-sparc-coder.
agent-tdd-london-swarm
Agent skill for tdd-london-swarm - invoke with $agent-tdd-london-swarm.
moai-workflow-tdd
Test-Driven Development workflow specialist using RED-GREEN-REFACTOR cycle for test-first software development. Use when developing new features from scratch or when behavior specification drives implementation.
Pair Programming
AI-assisted pair programming with multiple modes (driver$navigator$switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
V3 Security Overhaul
Complete security architecture overhaul for claude-flow v3. Addresses critical CVEs (CVE-1, CVE-2, CVE-3) and implements secure-by-default patterns. Use for security-first v3 implementation.
implement
Use in the Implement phase whenever writing or editing production Java code, or fixing a bug, in a Spring/Spring Boot project. Enforces test-first (red-green-refactor), executes the approved plan step by step, and honors the project's path-scoped tech-stack rules and the task's enforcement set. Preloaded into…