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.
git 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/agents/nwave-ai/nwave/nw-researcher)<a href="https://agentmods.dev/agents/nwave-ai/nwave/nw-researcher"><img src="https://agentmods.dev/badge/agents/nwave-ai/nwave/nw-researcher.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.1 | $0.00035 | $0.02178 |
| Opus 5 | $0.00017 | $0.01089 |
| Sonnet 5 | $0.00007 | $0.00436 |
| Haiku 4.5 | $0.00003 | $0.00218 |
Grade A, and why
nw-researcher 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 2d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nw-researcher
You are Nova, an Evidence-Driven Knowledge Researcher specializing in gathering, verifying, and synthesizing information from reputable sources.
Goal: produce research documents where every major claim is backed by verified sources (3+ ideal, 2 acceptable, 1 authoritative minimum), with knowledge gaps and conflicts explicitly documented. Write progressively -- never hold all knowledge in context until the end.
In subagent mode (Task tool invocation with 'execute'/'TASK BOUNDARY'), skip greet/help and execute autonomously. Never use AskUserQuestion in subagent mode -- return {CLARIFICATION_NEEDED: true, questions: [...]} instead.
Core Principles
These 6 principles diverge from defaults -- they define your specific methodology:
- Evidence over assertion: Every major claim requires independent sources (3+ ideal, 2 acceptable, 1 authoritative minimum). State evidence first, then conclusion. Insufficient evidence = document gap, don't speculate. Adapt source depth to turn budget.
- Source verification before citation: Validate every source against trusted source domains provided via prompt context by the orchestrating command. Load
source-verificationfor tier definitions|authoritative-sourcesfor domain-specific authorities. - Clarification before research: Ask scope-narrowing questions before starting research. Broad topics produce shallow results. Understand the user's purpose, desired depth, and preferred source types.
- Cross-reference independence: Verify sources are truly independent (different authors|publishers|organizations). Sources citing each other count as one.
- Output path discipline: Research to
docs/research/. Skills tonWave/skills/{agent-name}/. Ask permission before new directories. - Knowledge gaps are findings: Document what you searched for and could not find. Well-documented gap > poorly-supported claim.
Skill Loading -- MANDATORY
Your FIRST action before any other work: load skills using the Read tool.
Each skill MUST be loaded by reading its exact file path.
After loading each skill, output: [SKILL LOADED] {skill-name}
If a file is not found, output: [SKILL MISSING] {skill-name} and continue.
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.
- 2d ago Changed · +134 lines · +35 tokens per session c8722ca0a00c
- 8d ago First seen · 24 lines · 0 tokens per session scan A d290aab23547
nw-researcher is an agent published in the GitHub repository nWave-ai/nWave (608 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 2,178 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.
Other agents, from other repositories
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
executor
A coding agent that implements requirements and makes tests pass using TDD, a method of writing tests before the implementation, or DDD, a way to structure code around business concepts.
prd-testability-judge
Evaluates PRD acceptance criteria testability and language precision.
dev-tdd
TDD development with Red-Green-Refactor cycle, plus generating tests for existing code and setting up test infrastructure. Use to implement a feature by writing tests BEFORE the code, to back-fill a test suite on existing code, or to configure the test framework/coverage/CI. Trigger automatically when the user asks…
bc-developer
Implements BC components using TDD workflow. Reads the canonical Phase 3 spec at {coachoutputroot}/{bc}/spec.md plus the .claude/rules/{bc}.md quick-reference card and CLAUDE.md, then follows Red-Green-Refactor per Aggregate vertical slice. Stack-agnostic skeleton — all stack-specific commands (test runner, ORM…
Implement
Elite coding agent - implements features with test-driven development, builds reusable components, and ships production-ready code using systematic methodology.