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 quay/ai-helpers --skill eli5git clone --depth 1 https://github.com/quay/ai-helpersWrote 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/quay/ai-helpers/eli5)<a href="https://agentmods.dev/skills/quay/ai-helpers/eli5"><img src="https://agentmods.dev/badge/skills/quay/ai-helpers/eli5.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.00068 | $0.00433 |
| Opus 5 | $0.00034 | $0.00217 |
| Sonnet 5 | $0.00014 | $0.00087 |
| Haiku 4.5 | $0.00007 | $0.00043 |
Grade A, and why
eli5 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.
What it actually says
ELI5 — Explain Like I'm 5
Distill $ARGUMENTS into a short, clear explanation with a concrete code snippet or example. The audience is a senior engineer who wants the mental model, not a tutorial.
Format
Every response follows this structure:
1. One-liner (required)
One sentence: what it is, in plain terms.
2. Analogy (optional)
A one-sentence analogy only if it genuinely clarifies. Skip if forced.
3. Code snippet or concrete example (required)
A short, runnable snippet or real-world example that demonstrates the concept. Prefer examples in the current project's primary language and domain. Annotate with 1-2 inline comments only where non-obvious.
4. The gotcha (optional)
One sentence on the most common misconception or sharp edge, if one exists.
Rules
- Keep the entire response under 15 lines of prose (code doesn't count toward this).
- Never pad with disclaimers, caveats, or "it depends" hedging.
- Never explain what the user already knows — skip straight to the part they're asking about.
- If the question is about something in the current codebase, reference the actual code, not a hypothetical.
- Match the user's depth: if they ask "how does SSA work in controller-runtime", assume they know what controllers are.
Depth escalation
If the user asks for more detail, add ONE level of depth — internal mechanics, edge cases, or a second code snippet. Don't repeat the original explanation.
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 · 47 lines · 68 tokens per session scan A 4d06e89b17bf
eli5 is a skill published in the GitHub repository quay/ai-helpers (3 stars, last pushed 19d ago), licensed MIT. It adds 68 tokens to every session and 433 once invoked, about $0.0003 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-04.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.
master-yinguang
A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.