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-deepernpx skills add kavyabhand/claude-eli5 --skill eli-deepergit 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-deeper)<a href="https://agentmods.dev/skills/kavyabhand/claude-eli5/eli-deeper"><img src="https://agentmods.dev/badge/skills/kavyabhand/claude-eli5/eli-deeper.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.00063 | $0.00400 |
| Opus 5 | $0.00032 | $0.00200 |
| Sonnet 5 | $0.00013 | $0.00080 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade B, and why
eli-deeper 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" What it actually says
ELI5 Deeper — Step Up One Level
Move one step more technical on the level ladder, then re-explain the last concept at the new level.
The Level Ladder
eli5 (1) → eli-kid (2) → eli-teen (3) → eli-adult (4) → eli-expert (5)
↑ most technical
Steps
-
Check current level:
cat .claude/eli5-state.json 2>/dev/null || echo "none" -
Determine next level up:
- eli5 → eli-kid
- eli-kid → eli-teen
- eli-teen → eli-adult
- eli-adult → eli-expert (ask for their field if not saved in
.claude/eli5-expert-field) - eli-expert → already at max; tell the user in one sentence
-
Update state:
printf '{"level":"[new-level]","label":"[new-label]"}' > .claude/eli5-state.json -
Acknowledge the level change in one sentence at the NEW level's style.
-
Re-explain the most recent concept at the new level — don't just announce the switch. If no concept was recently explained, just confirm the new level is active.
Important
Apply the new level's rules immediately. Read the core rules at:
~/.claude/skills/eli5-mode/references/core-rules.md
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 · 48 lines · 63 tokens per session scan B 5d24e7257de0
eli-deeper is a skill published in the GitHub repository kavyabhand/claude-eli5 (21 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 400 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
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 "入职".
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
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
best-practices
Searchable knowledge base of 152+ programming best practices across 30+ languages and frameworks. BM25-powered search over curated resources from industry leaders (Google, Airbnb, Uber, Mozilla, Shopify, OWASP).
ark-documentation
Guidance for structuring Ark documentation using the Diataxis framework. Use this skill when creating new docs, deciding where content belongs, reviewing documentation PRs, or restructuring existing documentation.