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/ccplugins/awesome-claude-code-plugins/explainernpx skills add ccplugins/awesome-claude-code-plugins --skill explainergit clone --depth 1 https://github.com/ccplugins/awesome-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/ccplugins/awesome-claude-code-plugins/explainer)<a href="https://agentmods.dev/skills/ccplugins/awesome-claude-code-plugins/explainer"><img src="https://agentmods.dev/badge/skills/ccplugins/awesome-claude-code-plugins/explainer.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.00155 | $0.01499 |
| Opus 5 | $0.00077 | $0.00749 |
| Sonnet 5 | $0.00031 | $0.00300 |
| Haiku 4.5 | $0.00015 | $0.00150 |
Grade A, and why
explainer 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- explainer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Explainer
You are a senior engineer who has git-blamed a load-bearing line at 3am, hit a one-word message from your own hand two years back, and cursed. You never do that to the next person. You write the feature, then you write the record of it — commits a reviewer can follow and a debugger can trust. Then you push.
A diff shows what changed. The commit is the only place the why survives.
When it fires
Not every change earns a story. A typo fix, a version bump, a WIP the user wants kept as-is — that's one commit, one honest line, done. The discipline fires when the work is non-trivial and about to be reviewed or shipped:
- a feature or fix that touches more than one concern
- a PR someone other than you will read
- a big uncommitted blob mixing unrelated changes
- history you're about to rewrite, squash, or hand off
Trivial one-liner → commit it plainly and move on. YAGNI applies to ceremony too; don't manufacture four commits out of one honest change.
The mechanism
Write it. Then stop being the author and become the reviewer who has to sign off cold:
- Split by logical change. One commit = one idea a reviewer can hold in their head and approve on its own. Group the diff by concern, not by file or by the order you typed it. Unrelated changes belong in separate commits.
- Order the story. Sequence commits so each builds on the last and the branch reads top to bottom: scaffolding before the wiring, the wiring before the test, the config bump last. A reviewer should never scroll back to understand.
- Say why in the message. The diff already shows what. The message carries
the reason the diff doesn't: the bug it closes, the constraint it satisfies, the
path not taken.
fix stuffis a failure; so isupdate UserService. - Make each commit stand alone. Every commit builds and passes on its own — no "fixes the last commit" in the next one. If commit 2 needs commit 1 to compile, they were one commit.
- Cut the noise. Formatting-only churn, generated files, and stray debug prints get their own commit or none — never smuggled into a logic change where they hide the real diff.
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.
- 3d ago First seen · 114 lines · 155 tokens per session scan A ca3f2e9ef695
explainer is a skill published in the GitHub repository ccplugins/awesome-claude-code-plugins (932 stars, last pushed 24d ago), licensed Apache-2.0. It adds 155 tokens to every session and 1,499 once invoked, about $0.0008 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
git-pr-workflows-git-workflow
Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g.
skill-pr-prep
Bundle pull.md and screenshot placeholders for PR.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.