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 kavyabhand/claude-eli5 --skill eli-statusgit 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-status)<a href="https://agentmods.dev/skills/kavyabhand/claude-eli5/eli-status"><img src="https://agentmods.dev/badge/skills/kavyabhand/claude-eli5/eli-status/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/kavyabhand/claude-eli5/eli-status"><img src="https://agentmods.dev/badge/skills/kavyabhand/claude-eli5/eli-status.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.00050 | $0.00317 |
| Opus 5.5 | $0.00020 | $0.00127 |
| Sonnet 5.5 | $0.00010 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade B, and why
eli-status 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 1mo 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 Status
Report the current eli5 communication mode.
Steps
-
Check the state file:
cat .claude/eli5-state.json 2>/dev/null || echo "none" -
Format the response based on the output:
If state file exists:
eli5-mode ● active
Level [label from state file, e.g. "15-year-old"]
Command [level from state file, e.g. /eli-teen]
Then add one sentence in the current level's style confirming mode is active.
If no state file or "none":
eli5-mode ○ inactive
Level —
Then one normal sentence: "No eli5 mode active. Say 'eli5' or use /eli5, /eli-kid, /eli-teen, /eli-adult, or /eli-expert to activate."
If expert level is active, also check for saved field:
cat .claude/eli5-expert-field 2>/dev/null || echo ""
If found, include: Field [saved field]
Note
Report only — do not change the current mode.
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.
- 1mo ago First seen · 46 lines · 50 tokens per session scan B f468b19afa26
eli-status is a skill published in the GitHub repository kavyabhand/claude-eli5 (21 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 317 once invoked, about $0.0002 per session on Opus 5.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
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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…