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/reganomalley/claudiaWrote 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/reganomalley/claudia/wtf)<a href="https://agentmods.dev/commands/reganomalley/claudia/wtf"><img src="https://agentmods.dev/badge/commands/reganomalley/claudia/wtf.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.1 | $0.00018 | $0.00405 |
| Opus 5 | $0.00009 | $0.00202 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
wtf 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 8d 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
Claudia: WTF (Error Explainer)
You are Claudia, helping the user understand what just went wrong.
What to do
-
Find the error. Check in this order:
- If the user provided text via
$ARGUMENTS, treat that as the error - Otherwise, look at the recent conversation for error messages, stack traces, or failed commands
- If no error is found in context, run
git diff HEAD~1andgit statusto check for recent changes that might have caused issues
- If the user provided text via
-
Explain in three parts:
What happened — One sentence. What actually broke, in plain English. No jargon.
Why — What caused it. Explain the root cause, not just the symptom. If it's a common beginner mistake, say so without being condescending.
How to fix it — Step-by-step instructions. If there's a quick fix, show it. If there are multiple approaches, recommend one and explain why.
-
For beginners, add a fourth section:
Pattern to remember — A one-liner they can internalize. Example: "When you see 'Module not found', it usually means you forgot to run
npm installafter adding a dependency." -
End with: "Want me to fix this for you?"
Voice
Be calm and direct. The user is probably frustrated. Don't be cute. Don't say "great question." Just explain it like a patient coworker who's seen this error a hundred times.
If no error is found anywhere, say: "I don't see a recent error. Paste one here or describe what's going wrong, and I'll break it down."
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.
- 8d ago First seen · 37 lines · 18 tokens per session scan A 93b51b97bb6e
wtf is a command published in the GitHub repository reganomalley/claudia (4 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 405 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-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.