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 tech-explainergit 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/tech-explainer)<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/tech-explainer"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/tech-explainer/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/tech-explainer"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/tech-explainer.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.00119 | $0.04467 |
| Opus 5.5 | $0.00048 | $0.01787 |
| Sonnet 5.5 | $0.00024 | $0.00893 |
| Haiku 4.5 | $0.00012 | $0.00447 |
Grade A, and why
tech-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 13d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tech-explainer — make a stranger understand, and able to push back
The reader is intelligent but was not in the room. They did not watch the tests, they will not read the raw report, and they have their own opinion about what you should do. If you hand them the findings compressed, every conclusion looks like an assertion, and the conversation becomes credentials against credentials.
The job is not to summarise. The job is to transfer enough of the reasoning that the reader can disagree with you correctly. A reader who finishes and says "I still think it's the wrapper, and here's why your 3x number is wrong" is a success. A reader who nods and remembers nothing is a failure, even if they agreed.
What this skill gives you
| File | Use it for |
|---|---|
assets/skeleton.md |
Start here. The fill-in document. Copy it, then delete what has nothing to say. |
references/diagrams.md |
Copy-paste Mermaid for all six patterns, plus the syntax that bites. |
references/language.md |
Full STE rules, the rewrite table, and the mechanical rewrite pass. |
When this is NOT the right skill
- The reader must build something from the document →
explainer-doc. That skill produces an actionable spec (DDL, queries, acceptance criteria). This one produces understanding. - The reader already lived through the investigation →
technical-writingor a plain summary. The vocabulary table and STE discipline are overhead they don't need. - It's a README, API reference, or runbook →
technical-writing.
The tell for this skill: the reader will form or change an opinion, and you need that opinion to be based on the numbers rather than on trust.
The central move — rank the layers by size of effect
This is the single technique that makes the document work, and it is what most explainers get wrong.
What ships with it
4 files 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.
- 13d ago Changed · -1 lines · -23 tokens per session 2f93092e00db
- 19d ago Changed · -5 lines · -109 tokens per session e2e28bebf878
- 1mo ago First seen · 281 lines · 251 tokens per session scan A d70778d8a4b8
tech-explainer is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed 2d ago), licensed MIT. It adds 119 tokens to every session and 4,467 once invoked, about $0.0005 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-discover
Interview the user relentlessly about a decision until every branch of the design tree is resolved, then record the result as a short ADR.
goga-review-plan
Verify execution plan completeness and correctness.
goga-define-challenge
Challenge the complete product definition before the PRD is generated.
goga-task-by-specifying
Interactive task formulation from a raw request.
goga-prototype-type-detail
Per-type detailing (methods, properties, signatures) for the prototype pipeline.
goga-prototype-cell-distribution
Distributing types across cells and defining cell boundaries.