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/koolamusic/claudefilesWrote 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/koolamusic/claudefiles/explain)<a href="https://agentmods.dev/commands/koolamusic/claudefiles/explain"><img src="https://agentmods.dev/badge/commands/koolamusic/claudefiles/explain/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/koolamusic/claudefiles/explain"><img src="https://agentmods.dev/badge/commands/koolamusic/claudefiles/explain.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.00029 | $0.00400 |
| Opus 5.5 | $0.00012 | $0.00160 |
| Sonnet 5.5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
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 9d 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
Context
Front door for the explainer-formats skill. Usage:
/explain <topic> [--as <format>] [--level strict|80|light]
/explain <topic> as <format>
/explain formats
Defaults are --as ste and --level light. The topic can be a question, a pasted paragraph, a file path, or a symbol name. <format> is a rung (ste, diagram, html, video) or any visualizer diagram type (architecture, sequence, sankey, ...); the full list is references/formats.md in the skill.
Your task
- Load the
explainer-formatsskill and follow it. - If
$ARGUMENTSis exactlyformats(or empty apart from that word), print the skill'sreferences/formats.mdand stop. - Otherwise parse
$ARGUMENTS: everything before the first--asor--levelflag is<topic>; the flags set the format and the level. With no--as, a trailingas <format>(the lastasfollowed by one word) sets the format and is removed from the topic. A missing flag takes the default. A format that is neither a rung nor a visualizer type, or an unknown level, is an error; say which values are valid and stop. - Hand the skill
<topic> --as <format> --level <level>and return its output, including the closing line that offers the next rung.
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.
- 9d ago Changed · +3 lines b632ae7ace2d
- 12d ago First seen · 22 lines · 29 tokens per session scan A 8fc5a2661de2
explain is a command published in the GitHub repository koolamusic/claudefiles (130 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 400 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-10-06.
Other commands, from other repositories
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-0-8
A Japanese-language command that displays the current project setup progress.
setup-m365cli.es
Lesson command — Setup de M365 CLI.
prep-role
Deep prep for a specific role's interview process. The user wants to know what to expect, how to win, and what kills candidates at their level.
setup-vercel.es
Command "setup-vercel.es" from minicoohei/ai-agent-camp, covering configuración de vercel cli, step 0: verificar progreso de configuración, lo que hará en esta sesión, verificación de preparación and step 1: crear cuenta de vercel.