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 jackjin1997/ClawForge --skill five-whysgit clone --depth 1 https://github.com/jackjin1997/ClawForgeWrote 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/jackjin1997/clawforge/five-whys)<a href="https://agentmods.dev/skills/jackjin1997/clawforge/five-whys"><img src="https://agentmods.dev/badge/skills/jackjin1997/clawforge/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/jackjin1997/clawforge/five-whys"><img src="https://agentmods.dev/badge/skills/jackjin1997/clawforge/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.00193 | $0.01861 |
| Opus 5.5 | $0.00077 | $0.00744 |
| Sonnet 5.5 | $0.00039 | $0.00372 |
| Haiku 4.5 | $0.00019 | $0.00186 |
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 108 lines · 193 tokens per session scan A 5840b578fe28
five-whys is a skill published in the GitHub repository jackjin1997/ClawForge (13 stars, last pushed 4mo ago), with no licence file. It adds 193 tokens to every session and 1,861 once invoked, about $0.0008 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
arxiv-agentic-verifier
Source Paper: Scaling Agentic Verifier for Competitive Coding (ID: 4a4c4dae6a5145ebc4d62eb2d64b0f0f) Type: Code Verification / Test Generation.
pentest-ctf-binary
Binary exploitation (Pwn) and reverse engineering tools for CTF challenges and software analysis.
pentest-ctf-forensics
Digital forensics, steganography, and packet analysis for CTF challenges and investigation.
openclaw-tune
OpenClaw system-level maintenance — cleans sessions/.bak rotation, disk bloat under /.openclaw/, validates model fallback chain, audits cron health, prunes short-term-recall noise. Run after openclaw update or every 1-2 weeks. Different from workspace document tune-up (single-responsibility canonical .md files, token…
analyze-repo
Generate an evidence-backed visual architecture and technical-debt audit for an entire repository.
debug
Debug errors, test failures, incorrect output, browser failures, intermittent bugs, and performance regressions through a tight red/green diagnosis loop. Use when behavior is broken, failing, flaky, slow, or unexplained.