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 skills add nWave-ai/nWave --skill nw-deliver-orchestrationgit 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-deliver-orchestration)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-deliver-orchestration"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-deliver-orchestration/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/skills/nwave-ai/nwave/nw-deliver-orchestration"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-deliver-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.00981 |
| Opus 5 | $0.00024 | $0.00491 |
| Sonnet 5 | $0.00010 | $0.00196 |
| Haiku 4.5 | $0.00005 | $0.00098 |
Grade A, and why
nw-deliver-orchestration 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 8d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DELIVER Wave Orchestration
When invoked via *deliver "{feature-description}", Apex orchestrates the complete DELIVER wave lifecycle.
Orchestration Role
Parse feature description, derive feature ID, execute 9 phases in order. Track state for resume capability.
Invocation: *deliver "Implement user authentication with JWT tokens"
9 Phases
Phase 1-2: Baseline Creation + Review
Create: docs/feature/{feature-id}/deliver/baseline.yaml. Reviewer: @nw-software-crafter-reviewer.
Smart skip: yes (if file exists AND validation.status == "approved").
Phase 3-4: Roadmap Creation + Dual Review
Create: docs/feature/{feature-id}/deliver/roadmap.json.
Reviewer 1: @nw-product-owner-reviewer (business) | Reviewer 2: @nw-software-crafter-reviewer (technical). Sequential reviews.
Smart skip: yes (if approved).
Phase 5-6: Split + Review Each Step
Define steps in: docs/feature/{feature-id}/deliver/roadmap.json. Reviewer: @nw-software-crafter-reviewer (per roadmap step).
Smart skip: yes (if all approved).
Phase 7: Execute All Steps
For each step: invoke @nw-software-crafter with step ID. Automatic dependency ordering (topological sort via Kahn's algorithm). 11-phase TDD per step (PREPARE through COMMIT). Local commit after each step (no push). Stop immediately if any step fails.
Phase 8: Finalize
Archive to: docs/evolution/{timestamp}_{feature-id}.md. Clean up workflow files.
Phase 9: Report Completion
Display comprehensive statistics | List all quality gates passed | Show next steps (review evolution doc, push commits, proceed to DEVOPS wave validation).
Smart Skip Logic
- File exists AND
validation.status == "approved"-> skip creation, load for context - File exists but not approved -> skip creation, proceed directly to review
- File missing -> create new artifact
Quality Gates
| Gate | Reviews | Reviewer |
|---|---|---|
| Baseline | 1 | nw-software-crafter-reviewer |
| Roadmap | 2 | nw-product-owner-reviewer + nw-software-crafter-reviewer |
| Step files | N (per step) | nw-software-crafter-reviewer |
| TDD phases | 2N (per step) | REVIEW + POST-REFACTOR REVIEW |
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.
- 8d ago First seen · 97 lines · 48 tokens per session scan A 18c771bcc9cb
nw-deliver-orchestration is a skill published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 5d ago), licensed MIT. It adds 48 tokens to every session and 981 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
planning
Create structured plan documents and track work items using YAML frontmatter. Use when the user wants to plan a feature, track progress, log bugs/tasks/ideas, or organize project work.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.