A guide agent for answering questions about nWave, including its methods, project status, commands, migrations, and troubleshooting. It reads the project to provide answers that fit the current repository.

Use it to investigate nWave settings, understand project state, find commands, explore migration steps, or troubleshoot issues using the repository's own files.

It gives developers a place to ask how the project works without relying on memory or generic advice. Configuration questions require checking the project's canonical documentation first.

nw-buddy — Skill for Claude Code by nWave-ai

Install

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.

Any agent

npx skills add nWave-ai/nWave --skill nw-buddy

Clone the repo

git clone --depth 1 https://github.com/nWave-ai/nWave

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-buddy/github.svg)](https://agentmods.dev/skills/nwave-ai/nwave/nw-buddy)

Your own site

<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-buddy"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-buddy/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-buddy"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-buddy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,294 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00030	$0.01294
Opus 5	$0.00015	$0.00647
Sonnet 5	$0.00006	$0.00259
Haiku 4.5	$0.00003	$0.00129

Measured 9d ago against content hash 181707d7f0a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

nw-buddy 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 9d 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.

nWave/skills/nw-buddy/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

NW-BUDDY: nWave Concierge

Wave: CROSS_WAVE | Agent: Guide (nw-nwave-buddy) | Command: /nw-buddy

Overview

Ask questions about nWave — methodology, project state, commands, migration, troubleshooting. Guide reads your project and gives contextual answers.

Configuration questions — mandatory Read-tool instruction (D7)

Before answering ANY question about nWave configuration (rigor profile, documentation density, expansion mechanism, doc tiers, audit logging, etc.):

Read docs/reference/global-config.md using the Read tool — this is the canonical schema reference. Do NOT answer from training memory; configuration evolves and your training is not authoritative.
Read docs/guides/configuring-doc-density.md for the how-to perspective if the question is about changing settings.
Then answer with grounded specifics: cite the exact config key path, valid values, and link to the source doc.

Why: configuration drift between releases would otherwise cause stale answers. The reference doc is the contract. (See ADR-001-rigor-as-config-concern.md for the rigor/density inheritance decision.)

Expansion mechanism — answering "how do I see more detail?"

When the user asks how to see more detail in their feature documentation (or equivalent — "expand", "more rationale", "why this decision", "show alternatives"):

Explain the expand mechanism for wave commands: each wave (/nw-discover, /nw-discuss, /nw-design, /nw-devops, /nw-distill, /nw-deliver) accepts --expand <id> to render a specific Tier-2 rationale section into the wave's feature-delta.md without re-running the wave.
Mention the wave-end interactive prompt: when documentation.expansion_prompt = "ask", each wave ends with a menu listing available expansions; the user picks items by id and the wave appends them to feature-delta.md.
Provide example expansion identifiers — at minimum three across waves: jtbd-narrative (DISCUSS), alternatives-considered (DISCUSS), migration-playbook (DISCUSS), trade-off-analysis (DESIGN), c4-narrative (DESIGN), infra-cost-analysis (DEVOPS), runbook-drafts (DEVOPS), edge-case-enumeration (DISTILL), refactoring-journal (DELIVER). Each wave's full expansion catalog lives in its skill's "Output Tiers" section.

Read the full file on GitHub · 87 lines

Changes

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.

9d ago First seen · 87 lines · 30 tokens per session scan A 181707d7f0a0

Subscribe to this mod's changes

nw-buddy is a skill published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 1,294 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-08-30.

Building agents Claude Code DevOps and cloud TDD agentic-ai ai software-architecture

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.

wshobson/agents · 35 tokens

engineering-workflow

A Chinese-language workflow for reliable software development. It describes exploring the problem, making a plan, using TDD (test-driven development, where tests are written before the code), debugging methodically, reviewing code, and verifying the result.

TencentCloud/Octop · 47 tokens

nw-buddy