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 repowise-dev/modpack --skill five-whysgit clone --depth 1 https://github.com/repowise-dev/modpackWrote 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/repowise-dev/modpack/five-whys)<a href="https://agentmods.dev/skills/repowise-dev/modpack/five-whys"><img src="https://agentmods.dev/badge/skills/repowise-dev/modpack/five-whys/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/repowise-dev/modpack/five-whys"><img src="https://agentmods.dev/badge/skills/repowise-dev/modpack/five-whys.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.00055 | $0.00449 |
| Opus 5.5 | $0.00022 | $0.00180 |
| Sonnet 5.5 | $0.00011 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
five-whys 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.
What it actually says
five-whys mode
Activation: /five-whys, "activate five-whys", "five whys mode".
Deactivation: /default, "deactivate", "normal mode".
Protocol
Before writing any fix, output exactly this structure:
Why 1: <observed problem> → <immediate cause>
Why 2: <that cause> → <deeper cause>
Why 3: → <deeper cause>
Why 4: → <deeper cause>
Root: <root cause>
Fix: <proposed solution targeting the root, not the symptom>
Rules:
- Every Why must follow logically from the previous. No leaps.
- If a Why hits "unknown", run a tool (Read/Grep/Bash) to find out before continuing.
- Stop early only if the chain genuinely bottoms out before 5 (rare). Note "bottomed at Why N".
- The Fix targets the root, not Why 1.
Override
If user says "just fix it", "skip the whys", or similar at any point: acknowledge in one line ("Skipping chain — fixing directly."), then fix. User always has override.
When to apply
- Debugging a bug
- Performance issue
- Architecture decision
- Recurring incident
- Code review of a fix ("does this address the root?")
When to skip silently
- Trivial typo / rename / formatting
- New feature with no underlying problem to diagnose
- User explicitly asked for a quick patch
Boundaries
- Code correctness, syntax, error messages: unchanged
- Don't invent causes — if a Why requires guessing, investigate first
- Safety-critical bug → still run the chain, but state the immediate mitigation in line 1 before the chain
Token note
Adds ~150-300 tokens per fix. Worth it for non-trivial bugs.
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 · 57 lines · 55 tokens per session scan A 3598d7582fa2
five-whys is a skill published in the GitHub repository repowise-dev/modpack (19 stars, last pushed 6mo ago), licensed MIT. It adds 55 tokens to every session and 449 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-08-30.
Other skills, from other repositories
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
memory-leak-debug
Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.
bugfix
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.