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-continuenpx 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.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.00028 | $0.01127 |
| Opus 5 | $0.00014 | $0.00563 |
| Sonnet 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 today.
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.
- today First seen · 127 lines · 28 tokens per session scan A de46e250d197
nw-continue is a skill published in the GitHub repository nWave-ai/nWave (604 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 1,127 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
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
agent-repo-architect
Agent skill for repo-architect - invoke with $agent-repo-architect.
skill-reviewer
Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.