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/shawnclybor/clybor-claude-toolingWrote 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/shawnclybor/clybor-claude-tooling/five-whys)<a href="https://agentmods.dev/commands/shawnclybor/clybor-claude-tooling/five-whys"><img src="https://agentmods.dev/badge/commands/shawnclybor/clybor-claude-tooling/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/commands/shawnclybor/clybor-claude-tooling/five-whys"><img src="https://agentmods.dev/badge/commands/shawnclybor/clybor-claude-tooling/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.00015 | $0.00151 |
| Opus 5.5 | $0.00006 | $0.00060 |
| Sonnet 5.5 | $0.00003 | $0.00030 |
| Haiku 4.5 | $0.00002 | $0.00015 |
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 6d 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
Invoke the five-whys skill. Use when a tool failed twice, output is wrong despite correct-looking inputs, or you catch yourself about to retry blindly.
Usage
/five-whys
The skill prompts you for the problem statement and walks the protocol.
When to skip
- Routine errors with obvious fixes (typo, missing param, wrong path)
- Single-failure cases that obviously won't recur
When to invoke proactively
- About to retry the same call a third time
- A workflow produced wrong output and you don't know why
- An MCP returned unexpected data
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.
- 6d ago Changed 6d18d84275a4
- 1mo ago First seen · 27 lines · 15 tokens per session scan A a0770e05d4d6
five-whys is a command published in the GitHub repository shawnclybor/clybor-claude-tooling (6 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 151 once invoked, about $0.0001 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-31.
Other commands, from other repositories
forensics
Post-mortem investigation for failed or stuck workflows. Analyzes git history and planning artifacts.
audit-fix
Run audit, prioritize findings, auto-fix via quick tasks, test, and commit.
debug
Systematic debugging with hypothesis testing. Persistent across sessions.
scan
Analyze an existing codebase. Maps structure, architecture, conventions, and concerns.
gates-csk
Gate report — what the tool-level gates actually did, and which rules nothing has tripped.
add-phase
Add phase to end of current milestone in roadmap.