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-forgegit 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-forge)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-forge"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-forge/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-forge"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-forge.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.00044 | $0.00596 |
| Opus 5.5 | $0.00018 | $0.00238 |
| Sonnet 5.5 | $0.00009 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
nw-forge 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NW-FORGE: Create Agent (V2)
Wave: CROSS_WAVE Agent: Zeus (nw-agent-builder)
Overview
Create a new agent using research-validated v2 approach: focused core (200-400 lines) with Skills for domain knowledge.
- ANALYZE — Identify single clear responsibility, check overlap with existing agents, classify type, determine minimum tools needed. Gate: responsibility defined, no overlap, classification chosen.
- DESIGN — Select design pattern, define role and divergent principles, plan Skills extraction, draft frontmatter. Gate: pattern selected, principles drafted, frontmatter ready.
- CREATE — Write agent
.mdusing template. Workflow must be numbered task list. Create Skill files if domain knowledge exceeds 50 lines. Gate: agent file written, line count under 400. - VALIDATE — Run 14-point validation checklist. Check for anti-patterns. Verify workflow is numbered task list, not prose. Gate: all 14 items pass, zero anti-patterns.
- REFINE — Address validation failures. Add instructions only for observed failure modes. Re-measure and re-validate. Gate: all items pass, line count reported.
Agent Invocation
@nw-agent-builder
Execute *forge to create {agent-name} agent.
Configuration:
- agent_type: specialist | reviewer | orchestrator
- design_pattern: react | reflection | router | planning | sequential | parallel | hierarchical
Success Criteria
- Agent definition under 400 lines (
wc -l) - Official YAML frontmatter format (name, description, tools, maxTurns)
- 11-point validation checklist passes
- Only divergent behaviors specified (no Claude defaults)
- 3-5 canonical examples included
- Domain knowledge extracted to Skills if >50 lines
- No aggressive language (no CRITICAL/MANDATORY/ABSOLUTE)
- Safety via platform features (frontmatter/hooks), not prose
Next Wave
Handoff To: Agent installation and deployment Deliverables: Agent specification file + Skill files (if any)
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 · 55 lines · 44 tokens per session scan A 85b893aab2a6
nw-forge is a skill published in the GitHub repository nWave-ai/nWave (620 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 596 once invoked, about $0.0002 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
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.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
moai-run
Implement SPEC requirements using DDD/TDD methodology.
test-driven-development
Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
story-development
Implement user stories with test-driven development methodology.