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-continuegit 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-continue)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-continue"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-continue/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-continue"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-continue.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.00028 | $0.01127 |
| Opus 5.5 | $0.00011 | $0.00451 |
| Sonnet 5.5 | $0.00006 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
nw-continue 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NW-CONTINUE: Resume a Feature
Wave: CROSS_WAVE (entry point) | Agent: Main Instance (self — wizard) | Command: /nw-continue
Overview
Scans docs/feature/ for active projects, detects wave artifacts, displays progress summary, launches next wave command. Eliminates manual artifact inspection when returning after hours/days.
You (main Claude instance) run this wizard directly. No subagent delegation.
Behavior Flow
Step 1: Scan for Projects
If project ID provided as argument, use it directly.
Otherwise scan docs/feature/ for project directories:
ls -d docs/feature/*/
No directories found: Display "No active projects found under docs/feature/." Suggest /nw-new. Stop.
Step 2: Project Selection (Multiple Projects)
If multiple directories exist, list by most recent file modification:
find docs/feature/{feature-id}/ -type f -printf '%T@ %p\n' | sort -rn | head -1
Present via AskUserQuestion: project name|last modified date|most recent first. Ask user to select.
Step 3: Wave Progress Detection
Check each wave's artifacts using Wave Detection Rules in ~/.claude/nWave/skills/common/wizard-shared-rules.md.
Step 4: Anomaly Detection
Check before showing progress:
Empty/corrupted artifacts: Verify file size > 0 for each "complete" artifact. If empty, flag: "Warning: user-stories.md exists but is empty (0 bytes). Recommend re-running DISCUSS wave."
Non-adjacent waves (skipped): If artifacts exist for non-consecutive waves (e.g., DISCUSS + DELIVER but no DESIGN/DISTILL), warn with options:
- Fill the gap — start from missing wave
- Continue as-is
- Show all artifacts for manual review
Step 5: DELIVER Progress Detail
If DELIVER in progress, show step-level detail:
- Read
docs/feature/{id}/deliver/execution-log.json— count COMMIT/PASS steps, find first without COMMIT/PASS - Read
.develop-progress.jsonif exists: check last failure point - Display: "DELIVER in progress: Steps 01-01 through 02-01 complete. Next: 02-02"
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 · 127 lines · 28 tokens per session scan A de46e250d197
nw-continue is a skill published in the GitHub repository nWave-ai/nWave (620 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,127 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-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…
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.
bo-risk-assessment
A method for assessing operational risks in a process, project, or supplier arrangement using observed facts, possible consequences, and practical response suggestions. It keeps the likelihood of a consequence conditional unless the evidence supports more.
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.
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.