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 skills/melodic-software/claude-code-plugins/explainnpx skills add melodic-software/claude-code-plugins --skill explaingit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWrote 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/melodic-software/claude-code-plugins/explain)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/explain"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/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.00221 | $0.01993 |
| Opus 5 | $0.00111 | $0.00996 |
| Sonnet 5 | $0.00044 | $0.00399 |
| Haiku 4.5 | $0.00022 | $0.00199 |
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 yesterday.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Explain one thing, once, in genuinely plain words. The object can be a concept, a piece of code, an error, an architecture, or the assistant's own previous output. The core move is an altitude drop: land the explanation at the lowest useful altitude first, a concrete analogy, zero jargon, then layer altitude back up only when the user asks for it. The Feynman technique is the method.
Use when: the user signals they didn't follow something, I don't get it,
explain simply, what does this actually mean, rephrase that. Skip
when: the user wants ongoing, multi-session coaching with persistent state (hand
off to /education:teach); a plain inline answer already lands (just answer).
This skill auto-invokes (no disable-model-invocation) because "I don't get it"
should reach it without the user naming a command. Auto-trigger is best-effort;
/education:explain is the guaranteed path.
The core move. Plain-language first pass
- Identify the object. With an argument, that is the thing. Empty argument → the previous assistant response (see "Empty argument" below). Done when you can name the object in one sentence, or, on a cold start with no prior assistant message, have asked what to explain instead of guessing.
- Ground it, don't recall it. Re-read the actual artifact this turn, the message just sent, the file, the error text, the code. For an external concept, fetch a primary source rather than leaning on parametric memory (plugin doctrine: knowledge is grounded, not remembered). Done when this turn's explanation cites a specific passage, file, error text, or fetched primary source you re-read here. A recalled paraphrase does not count.
- Drop to plain. One concrete analogy from everyday life. No jargon, no term that itself needs prior knowledge. Short. If a technical word is unavoidable, define it inline in ordinary words the first time. Done when the explanation contains one everyday analogy whose structure maps to the object, a "what it's actually doing" line, and no leftover term that is not defined inline in ordinary words.
- Close with the handoff line (see "Handoff").
Done when the response ends with the single standard
/education:teachinvitation line.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 140 lines · 221 tokens per session scan A 4bf27fc951ca
explain is a skill published in the GitHub repository melodic-software/claude-code-plugins (15 stars, last pushed today), licensed MIT. It adds 221 tokens to every session and 1,993 once invoked, about $0.0011 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-09-03.
Other skills, from other repositories
count-combinations
For probability and counting: permutations, combinations, sample spaces, Monte Carlo simulation, brute-force enumeration, card/dice problems.
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
career-path-planner
Career goal mapping with skill gap analysis, actionable development plans, and milestone tracking. Use when planning career transitions, identifying skill gaps, setting professional development goals, or evaluating career options.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
course-material-creator
Create custom educational materials including syllabi, lesson plans, assessments, reading lists, and learning objectives. Use when building course curricula, training programs, workshops, or educational content.
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…