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/kavyabhand/claude-eli5/eli-docnpx skills add kavyabhand/claude-eli5 --skill eli-docgit clone --depth 1 https://github.com/kavyabhand/claude-eli5Wrote 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/kavyabhand/claude-eli5/eli-doc)<a href="https://agentmods.dev/skills/kavyabhand/claude-eli5/eli-doc"><img src="https://agentmods.dev/badge/skills/kavyabhand/claude-eli5/eli-doc.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.00064 | $0.00967 |
| Opus 5 | $0.00032 | $0.00483 |
| Sonnet 5 | $0.00013 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade B, and why
eli-doc scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/eli5-state.json 2>/dev/null || echo "none" How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ELI5 Doc — Generate Plain-Language Codebase Glossary
Scan the current codebase and write ELI5.md — a plain-language guide to everything in it.
Steps
1. Discover the codebase
# Get a high-level picture
find . -type f \( -name "*.py" -o -name "*.ts" -o -name "*.js" -o -name "*.go" \
-o -name "*.rs" -o -name "*.rb" -o -name "*.java" -o -name "*.cs" \) \
-not -path "*/node_modules/*" -not -path "*/.git/*" -not -path "*/dist/*" \
-not -path "*/build/*" | head -60
Also check for: README.md, package.json, pyproject.toml, Cargo.toml, go.mod
to understand the project's purpose.
2. Check eli5 level
cat .claude/eli5-state.json 2>/dev/null || echo "none"
Default to eli-adult level for docs (smart non-expert reader) unless a different level is currently active or the user specifies one.
3. Identify concepts to document
From the codebase, extract:
- What the project does (1-paragraph overview)
- Key concepts — domain terms, patterns, architectural decisions
- Main components — important files, classes, modules (top 10–15)
- How data flows — what comes in, what happens, what comes out
- Jargon the codebase uses — tech terms that appear frequently
4. Write ELI5.md
Use this structure:
# [Project Name] — Plain Language Guide
> Generated by eli5-mode. Level: [current level]. Updated: [date]
## What this project does
[2–3 sentences. Analogy-first. No jargon. What problem does it solve?]
## The big picture
[Optional: a flow diagram in words — "First X happens. Then Y. Finally Z."]
## Key concepts
### [Concept 1]
[Analogy-first explanation at the current level. 2–4 sentences.]
### [Concept 2]
[Same format]
[...continue for all key concepts...]
## Main files and what they do
| File | What it does (plain language) |
|---|---|
| `src/index.ts` | [plain description] |
| `src/auth.ts` | [plain description] |
## How data moves through the system
[Narrative walkthrough. Use concrete analogies. Walk through a typical request/action.]
## Words this project uses a lot
| Term | What it really means |
|---|---|
| [term] | [plain-language definition via analogy] |
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.
- 6d ago First seen · 111 lines · 64 tokens per session scan B 19583f2d1bc5
eli-doc is a skill published in the GitHub repository kavyabhand/claude-eli5 (21 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 967 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
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-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…