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/drn/dots/eli5npx skills add drn/dots --skill eli5git clone --depth 1 https://github.com/drn/dotsWhat 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.00054 | $0.00581 |
| Opus 5 | $0.00027 | $0.00291 |
| Sonnet 5 | $0.00011 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
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 2d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explain Like I'm 5
Break down a topic so a 5-year-old could understand it.
Arguments
$ARGUMENTS- The topic, concept, code, error message, or architecture decision to explain
Instructions
Step 1: Identify the topic
Read $ARGUMENTS. If empty, ask the user what they want explained and stop.
The topic can be anything:
- A programming concept (e.g., "recursion", "dependency injection")
- A piece of code (read the file or selection first)
- An error message or stack trace
- An architecture decision or system design
- A non-technical concept
If the topic references a file or code, read it before explaining.
Step 2: Explain it using the ADEPT pattern
Structure your explanation in this order:
-
Core idea first. State what it is in one plain sentence. No jargon, no acronyms unless you define them immediately. This is the "headline" -- if the reader stops here, they still learned something.
-
Analogy. Connect the concept to something from everyday life -- toys, food, playgrounds, animals, building blocks, a library, a kitchen. Pick an analogy that maps well to the actual mechanics, not just the surface.
-
Diagram (when visual). If the concept has structure, flow, or relationships, include a short ASCII diagram. Keep it under 10 lines. Skip this for purely abstract concepts where a diagram would not help.
-
Example. Walk through one concrete, minimal example. For code concepts, show 3-5 lines of real code with a one-line comment. For non-code topics, give a specific scenario.
-
Plain-English summary. One sentence a child could repeat back. Connect the analogy to the real thing: "So [analogy] is like [real thing] because..."
Rules:
- Use short sentences. Active voice. Simple words.
- Do not hedge, qualify, or add caveats. Be confident and direct.
- Accuracy matters but simplicity wins -- leave out details that do not help understanding.
- If the topic has multiple parts, build up layer by layer. Start with the simplest piece and add complexity one step at a time.
- Maximum 2-3 short paragraphs of prose per section. Brevity is the goal.
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.
- 2d ago First seen · 53 lines · 54 tokens per session scan A c7538223df6a
eli5 is a skill published in the GitHub repository drn/dots (23 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 581 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…