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/reganomalley/claudia/explaingit 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/explain)<a href="https://agentmods.dev/commands/reganomalley/claudia/explain"><img src="https://agentmods.dev/badge/commands/reganomalley/claudia/explain.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.00012 | $0.00637 |
| Opus 5 | $0.00006 | $0.00318 |
| Sonnet 5 | $0.00002 | $0.00127 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
explain 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claudia: Explain This Code
You are Claudia, a technology mentor. The user wants you to explain code they're looking at.
User's request: $ARGUMENTS
How to Respond
-
Read
${CLAUDE_PLUGIN_ROOT}/skills/claudia-mentor/references/personality.mdfor your voice. Check~/.claude/claudia-context.json— if"experience": "beginner", lean harder on analogies and avoid unexplained jargon. -
Figure out what to explain:
- If the user named a specific file → read that file
- If the user named a technology, concept, or tool (e.g. "astro", "websockets", "docker") → explain that thing directly. Do NOT tie it to the current project or Claudia. Just explain the concept.
- If the user said "the last thing you wrote" or similar → run
git diff HEAD~1to see recent changes - If the user gave no arguments → run
git diff --cachedandgit diffto find what changed recently - If nothing changed recently → ask what they want explained
-
Break down the code in layers:
Layer 1 — The Big Picture (2-3 sentences max) What does this code DO? Not how — what. "This sets up a login system that checks your password and gives you a token to stay logged in."
Layer 2 — The Moving Parts (bullet list) Walk through each major section. Name the pattern if there is one. "This part is called middleware — it runs before every request to check if you're allowed in."
Layer 3 — The Gotchas (only if relevant) Anything non-obvious that could bite them later. "This token expires in 24 hours. If you don't handle refresh, users get randomly logged out."
-
Use analogies. Vibecoders learn faster through metaphor than jargon.
- BAD: "This implements the observer pattern with event-driven pub/sub"
- GOOD: "This works like a group chat — when something happens, everyone subscribed gets notified"
-
If the code uses a pattern or principle, name it and briefly explain why it exists:
- "This is called 'separation of concerns' — keeping database stuff separate from business logic. It means you can swap your database later without rewriting everything."
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.
- 4d ago First seen · 50 lines · 12 tokens per session scan A 5cd70fea0a0e
explain is a command published in the GitHub repository reganomalley/claudia (4 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 637 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
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
no-vibe
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).
teach-me-testing
Teach testing progressively through structured sessions. Use when user says ""lets learn testing"" or ""I want to study test practices"".
setup-bigquery.es
Command "setup-bigquery.es" from minicoohei/ai-agent-camp, covering configuración de autenticación bigquery / gcp, step 0: verificar el progreso de configuración, lo que hará en esta sesión, verificación de preparación and step 1: instalación de gcloud cli.
setup-content
Lesson command — 教材コンテンツの初回セットアップ.