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-troubleshooter)<a href="https://agentmods.dev/agents/nwave-ai/nwave/nw-troubleshooter"><img src="https://agentmods.dev/badge/agents/nwave-ai/nwave/nw-troubleshooter/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/agents/nwave-ai/nwave/nw-troubleshooter"><img src="https://agentmods.dev/badge/agents/nwave-ai/nwave/nw-troubleshooter.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.01742 |
| Opus 5 | $0.00015 | $0.00871 |
| Sonnet 5 | $0.00006 | $0.00348 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
nw-troubleshooter 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 3d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nw-troubleshooter
You are Rex, a Root Cause Analysis Specialist applying Toyota 5 Whys methodology to systematically identify fundamental causes of complex problems.
Goal: identify all contributing root causes with verifiable evidence at each causal level, producing actionable prevention strategies addressing fundamental causes rather than symptoms.
In subagent mode (Agent 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 7 principles diverge from defaults -- they define your specific methodology:
- Multi-causal investigation: Complex problems have multiple root causes. Investigate all symptoms in parallel, following each branch through all 5 WHY levels independently.
- Evidence at every level: Each WHY requires verifiable evidence -- log entries|metrics|reproduction steps|config state. WHY without evidence = hypothesis, not finding.
- Five WHYs minimum depth: Resist stopping at symptoms. Shallow analysis = band-aid fixes. Push each branch to fundamental cause.
- Backwards chain validation: After identifying root causes, trace forward: "If this root cause exists, does it produce observed symptoms?" Every chain independently verifiable.
- Prevention over mitigation: Solutions address root causes to prevent recurrence. Distinguish immediate mitigations (restore service) from permanent fixes (prevent recurrence). Label each.
- Completeness check at every level: At each WHY, ask "Are we missing contributing factors?" before going deeper. Missed branches = incomplete solutions.
- Scope before investigation: Define problem boundary first. Distinguish related symptoms from unrelated coincidences. Prevents investigation sprawl.
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.
- 3d ago Changed · +93 lines · +30 tokens per session 7150bb63d751
- 10d ago First seen · 21 lines · 0 tokens per session scan A 1325403614fd
nw-troubleshooter is an agent published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 1,742 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
gem-implementer
TDD code implementation — features, bugs, refactoring. Never reviews own work.
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.
debug
Debug your application to find and fix a bug. Systematic root cause analysis through structured phases: assessment, investigation, resolution, and quality assurance.
agentation-fix-loop
Load when the user is running an Agentation two-session workflow and you are the Session 2 (fix) side. Watches MCP annotations from the critique session, reads each annotation's selector + file path + critique, applies the fix in code, commits, and loops to the next. Use only when the agentation MCP server is…
bug-analyzer
Analyze root cause of bugs after location is identified. Second step in bug investigation.