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-diagramgit 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-diagram)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-diagram"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-diagram/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-diagram"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-diagram.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.00033 | $0.00557 |
| Opus 5 | $0.00016 | $0.00279 |
| Sonnet 5 | $0.00007 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
nw-diagram 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 6d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NW-DIAGRAM: Architecture Diagram Generation
Wave: CROSS_WAVE | Agent: Morgan (nw-solution-architect) | Command: *create-diagrams
Overview
Generate architecture diagrams from design documents. Supports C4 model levels (context|container|component) in Mermaid|PlantUML|C4 format. Audience-appropriate: high-level context for stakeholders|component details for developers|deployment topology for operations.
Context Files Required
- docs/product/architecture/brief.md (SSOT — component boundaries, technology stack, design decisions)
Workflow
- Read Context — Load
docs/product/architecture/brief.md. Extract component boundaries, technology stack, and design decisions. Gate: architecture brief loaded. - Resolve Configuration — Determine
diagram_type(component|deployment|sequence|data|context),format(mermaid|plantuml|c4),level(context|container|component), andoutput_directory. Gate: all configuration parameters resolved. - Invoke Agent — Delegate to
@nw-solution-architectwith*create-diagramsfor{architecture-component}, passing context files and resolved configuration. Gate: agent invoked with all parameters. - Validate Output — Verify diagrams render without syntax errors and files exist in
output_directory. Gate: all success criteria pass. - Handoff — Return deliverables to invoking agent. Gate: architecture diagrams available in configured format.
Success Criteria
- Diagrams accurately represent current architecture
- Audience-appropriate detail level applied
- Diagrams render without syntax errors
- Output files created in configured directory
Next Wave
Handoff To: {invoking-agent-returns-to-workflow} Deliverables: Architecture diagrams in configured format
Examples
Example 1: Generate C4 container diagram
/nw-diagram payment-service --diagram_type=component --format=mermaid --level=container
Morgan reads architecture docs and produces a Mermaid container diagram showing service boundaries, data stores, and external integrations.
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.
- 6d ago First seen · 56 lines · 33 tokens per session scan A 10383f2094c4
nw-diagram is a skill published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 557 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-09-03.
Other skills, from other repositories
okf-openapi
OpenAPI/Swagger connector that produces and ingests Open Knowledge Format (OKF) bundles from an API contract. Parses an OpenAPI 3.x or Swagger 2.0 spec (JSON or YAML) into one concept per operation (API Endpoint) and per component schema (Schema), links endpoints to the schemas they reference as typed cross-links, and…
sinch-fax-api
Send and receive faxes programmatically with Sinch Fax API. Use when building fax workflows, fax-to-email delivery, sending PDFs by fax, checking fax status, managing fax services, configuring cover pages, receiving fax webhooks, or integrating fax into healthcare, legal, or financial applications.
thesaurus-get-{word}
Returns synonyms and antonyms for the given word.
backend-development
Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
pdf-fill
Fill PDF form fields from a data dict.