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 skills add saajunaid/caddis-plugin --skill explainer-docgit clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/explainer-doc)<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/explainer-doc"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/explainer-doc/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/skills/saajunaid/caddis-plugin/explainer-doc"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/explainer-doc.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.00086 | $0.01644 |
| Opus 5.5 | $0.00034 | $0.00658 |
| Sonnet 5.5 | $0.00017 | $0.00329 |
| Haiku 4.5 | $0.00009 | $0.00164 |
Grade A, and why
explainer-doc 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 19d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
explainer-doc — write for the reader who has no other context
A spec written by the people who did the investigation is unreadable by the team who must implement it. The authors compress away the reasoning, so every design choice looks arbitrary, and the reader either follows it blindly or argues with it. The fix is not "add more detail" — it is to lead with why, and to make the document survive being read alone.
Proven in anger on a Genesys→ETL cutover spec handed to an external vendor team. The user's verdict:
"nailed it — the document was perfect, simple, this should be the standard for explainer documents."
Reference implementation to study: a fleet app/docs/genesys-cutover/etl-implementation-spec.md (full
spec) and pega-cticallid-change-request.md (the same pattern compressed to one page for a single ask).
When this is NOT the right skill
If the reader already lived through the investigation (a teammate, your future self, an internal
handoff with shared context), use technical-writing or writing-plans instead — those are lighter
and don't need the "assume zero shared context" discipline below. Reach for explainer-doc specifically
when the reader is a stranger to the problem: an external vendor, a different team, a contractor,
anyone who will act on the document with no one in the room to ask.
The shape — in order. The order IS the pattern
Do not reorder these. Each section's position is load-bearing: later sections lean on earlier ones for their justification, and a reader working top-to-bottom needs the "why" before the "what."
| § | Section | Why it must come here |
|---|---|---|
| 1 | Why this exists — what broke, in a diagram | Every later decision is justified by this. Lead with the failure, not the solution. |
| 2 | What we're asking for, in one picture + a size table | The reader decides here whether the ask is reasonable. Include what you are explicitly not asking for. |
| 3 | Understanding the source data — the 3-5 things that catch people out | Each one should have already caused a real bug. Not a data dictionary. |
| 4 | The one thing that matters most | Usually not the new build. Say so plainly, with the number that proves it. |
| 5 | Where it runs + access needed | The blocker nobody writes down until the first deploy fails. |
| 6 | What to build, with the reasoning beside each choice | Not in an appendix. Next to the DDL / the query / the config. |
| 6b | Changes to what already exists | Always under-specified. Ask "what did I only half-mention?" — this is where the gaps hide. |
| 7-8 | The actual implementation (extract/build queries, load procedure, etc.) | |
| 9 | Schedule / retention / first load | The one-off backfill is always forgotten. |
| 10 | Validation, with EXPECTED VALUES | "Run this, expect ~64%" beats "verify the data." |
| 11 | Priority · acceptance (who signs off) · what we excluded | The exclusion list stops speculative building. |
| 12 | Glossary | Every acronym, inline. Not a link. |
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.
- 19d ago Changed · -55 tokens per session a70a7756dc4a
- 1mo ago Changed 0fefdca5f927
- 1mo ago First seen · 98 lines · 141 tokens per session scan A 21611be270bf
explainer-doc is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 1,644 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
goga-cookbook
Principles for applying DSL specification in cell and CODEMANIFEST design.
goga-review-plan
Verify execution plan completeness and correctness.
goga-define-challenge
Challenge the complete product definition before the PRD is generated.
goga-define-experience
Define the user experience required to achieve the established product goals and solve the identified problem.
goga-define-requirements
Define the product requirements that describe what the product must do to deliver the established user experience and achieve the agreed product goals.
goga-task-by-specifying
Interactive task formulation from a raw request.