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-fast-forwardgit 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-fast-forward)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-fast-forward"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-fast-forward/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-fast-forward"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-fast-forward.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 28 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00020 | $0.01341 |
| Opus 5 | $0.00010 | $0.00671 |
| Sonnet 5 | $0.00004 | $0.00268 |
| Haiku 4.5 | $0.00002 | $0.00134 |
Grade A, and why
nw-fast-forward 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 5d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NW-FAST-FORWARD: Fast-Forward
Wave: CROSS_WAVE (entry point) | Agent: Main Instance (self — orchestrator) | Command: /nw-fast-forward
Overview
Chains remaining waves end-to-end after single user confirmation. Detects current progress (like /nw-continue), shows planned sequence, runs each wave automatically — DISCUSS > DESIGN > DEVOPS > DISTILL > DELIVER — without stopping between waves.
You (main Claude instance) run this orchestration directly. Each wave invoked by reading its task file.
DISCOVER skipped by default — requires interactive customer interview data that cannot be auto-generated. Use --from=discover to include.
Behavior Flow
Step 1: Input Parsing
Accept: feature description (new project)|--from flag with optional feature ID|no arguments (auto-detect from docs/feature/)
Step 2: Project Resolution
New project (description provided): Derive feature ID per ~/.claude/nWave/skills/common/wizard-shared-rules.md (Feature ID Derivation). Show derived ID, allow override via AskUserQuestion. Create docs/feature/{feature-id}/.
Existing project (no description): Scan docs/feature/ (same as /nw-continue Step 1-2). If multiple, ask user to select.
Step 3: Detect Current Progress
Check wave artifacts using Wave Detection Rules in ~/.claude/nWave/skills/common/wizard-shared-rules.md.
Step 4: Determine Wave Sequence
Default order (DISCOVER skipped): DISCUSS > DESIGN > DEVOPS > DISTILL > DELIVER
With --from flag: Validate prerequisite artifacts exist. If missing: "Cannot start from {wave} — {missing} artifacts missing. Run /nw-continue to fill the gap." Start from specified wave.
Without --from: Find first incomplete wave, start from there.
Step 5: Show Plan and Confirm
Feature: {feature-id}
Fast-forward plan:
1. DISCUSS — Define requirements and user stories
2. DESIGN — Architecture and technology selection
3. DEVOPS — Platform and infrastructure readiness
4. DISTILL — Acceptance tests (Given-When-Then)
5. DELIVER — TDD implementation
This will run all 5 waves without stopping for 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.
- 5d ago First seen · 162 lines · 20 tokens per session scan A 24be84dbe327
nw-fast-forward is a skill published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 1,341 once invoked, about $0.0001 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.
organize-task-files
Lists, pairs, deduplicates, and moves task files across the Coworker task state machine (0draft → 6git-pushed). Use when asked to organize, clean up, or audit task files.