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 agentmods add commands/nikiforovall/claude-code-rules/five-whysgit clone --depth 1 https://github.com/NikiforovAll/claude-code-rulesWrote 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/commands/nikiforovall/claude-code-rules/five-whys)<a href="https://agentmods.dev/commands/nikiforovall/claude-code-rules/five-whys"><img src="https://agentmods.dev/badge/commands/nikiforovall/claude-code-rules/five-whys.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 | $0.00016 | $0.00341 |
| Opus 5 | $0.00008 | $0.00170 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
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 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.
What it actually says
Five Whys Analysis
Use the "Five Whys" root cause analysis technique to deeply understand problems.
Process:
1. Define the Problem
Clearly state the issue or symptom
2. Ask "Why?" Five Times
- Why did this problem occur? → Answer 1
- Why did Answer 1 happen? → Answer 2
- Why did Answer 2 happen? → Answer 3
- Why did Answer 3 happen? → Answer 4
- Why did Answer 4 happen? → Answer 5 (Root Cause)
3. Validate Root Cause
- Verify the logical chain
- Check if addressing root cause prevents recurrence
- Consider multiple root causes if applicable
4. Develop Solutions
- Address the root cause, not just symptoms
- Create preventive measures
- Consider systemic improvements
Example:
Problem: Application crashes when processing large files
- Why? → The application runs out of memory
- Why? → It loads entire file into memory at once
- Why? → The file parser wasn't designed for streaming
- Why? → Initial requirements only specified small files
- Why? → Requirements gathering didn't consider future growth
Root Cause: Incomplete requirements gathering process Solution: Implement streaming parser and improve requirements process
Best Practices:
- Focus on process, not people
- Look for systemic issues
- Document the analysis
- Involve relevant stakeholders
- Test solutions address root cause
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 First seen · 48 lines · 16 tokens per session scan A c2e0e5e72790
five-whys is a command published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 5d ago), licensed Apache-2.0. It adds 16 tokens to every session and 341 once invoked, about $0.0001 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 commands, from other repositories
derive-tests
Turn documented intent into a test-coverage map — inventory the tests that exist today, derive use-case cases from the system docs, separate existing coverage from proposed tests and unverified gaps, mark each unit / guarded-live / manual, and recommend a green-before-merge CI gate.
ship-check
Turn a vibe-coded repo into a reviewer-ready shipping packet — document the app, wire agent context, run security and performance audits, map test coverage, and compile the results.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
write-prd
Create a comprehensive Product Requirements Document from a feature idea or problem statement.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.
plan-launch
Create a full go-to-market strategy — beachhead segment, ICP, messaging, channels, and launch plan.