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-spikegit 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-spike)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-spike"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-spike/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-spike"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-spike.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.00062 | $0.02839 |
| Opus 5.5 | $0.00025 | $0.01136 |
| Sonnet 5.5 | $0.00012 | $0.00568 |
| Haiku 4.5 | $0.00006 | $0.00284 |
Grade A, and why
nw-spike scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
Phase 3: agent refactors the probe into `src/des/cli/wave_matrix.py` with a `wave-matrix` CLI command; one acceptance test exercises `subprocess.run(["wave-matrix", "--feature", "alpha"])` end-to-end and asserts the mark How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NW-SPIKE: Probe → Walking Skeleton
Wave: SPIKE (between DISCUSS and DESIGN) | Agent: Attila (nw-software-crafter) | Command: /nw-spike
Overview
Execute a two-phase wave that turns a risky assumption into visible, iterable value as fast as possible:
- PROBE — quick throwaway validation of one core assumption (30-60 min, code in
/tmp/) - PROMOTION GATE (interactive) — ask the user whether to promote the probe
- WALKING SKELETON — refactor the probe into an end-to-end thin slice committed to the repository (1-3 h, code in
src/+ 1 acceptance test)
The PROBE answers "does the mechanism work?". The WALKING SKELETON answers "can a user see it working end-to-end?". You never throw away working validated code — you promote it and iterate.
When to use
The spike is needed when the feature introduces:
- A new mechanism never tried in this codebase
- A performance requirement that cannot be validated by reasoning alone
- An external integration with unknown behaviour
If none of the above apply, skip SPIKE and go to DESIGN.
Prior Wave Consultation
- DISCUSS artifacts: Read
docs/feature/{feature-id}/discuss/(required)user-stories.md— scope and acceptance criteriawave-decisions.md— constraints and assumptions to test
- DIVERGE artifacts: Read
docs/feature/{feature-id}/diverge/recommendation.md(if present)
Interactive decision points (Phase 1 entry)
Decision 1: Probe scope
Question: What is the ONE assumption you need to validate? Examples:
- "Can we parse pytest output reliably in <5 seconds?"
- "Can the CEL library evaluate 100 expressions in <1 second?"
- "Can we write to
.git/hooks/from a subprocess without corruption?"
Decision 2: Performance budget
Question: What is the timing constraint? (Enter "none" if mechanism validation only) Examples:
- "<5 seconds end-to-end"
- "<100ms per operation"
- "Handle 10K items without OOM"
Decision 3: End-to-end path preview
Question: If this probe works, what would the thinnest end-to-end slice look like?
Capture the rough path: user-facing entry → business logic → persistence/services → user-visible output. This is not a commitment — it's context for the promotion gate later.
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 · 242 lines · 62 tokens per session scan A ed8675fa8a8d
nw-spike is a skill published in the GitHub repository nWave-ai/nWave (622 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 2,839 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other skills, from other repositories
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
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.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
testing
Testing: TDD, E2E, preferred patterns, test-value audits, verification, agent testing.
visual-regression
Detect unintended UI changes with reproducible rendered screenshots and reviewed baselines. Use when adding screenshot checks or investigating layout/theme regressions; do not approve a changed image merely to make the test green.