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-comparegit 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-compare)<a href="https://agentmods.dev/skills/kavyabhand/claude-eli5/eli-compare"><img src="https://agentmods.dev/badge/skills/kavyabhand/claude-eli5/eli-compare/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-compare"><img src="https://agentmods.dev/badge/skills/kavyabhand/claude-eli5/eli-compare.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.00066 | $0.00518 |
| Opus 5.5 | $0.00026 | $0.00207 |
| Sonnet 5.5 | $0.00013 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
eli-compare 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 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.
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
ELI-COMPARE — Side-by-Side Comparison
Usage: /eli-compare X vs Y or /eli-compare X Y
Extract the two concepts from the prompt. If only one is mentioned, ask: "Compare it to what?"
Format
**[Concept A]** — [one-line analogy from everyday life]
**[Concept B]** — [one-line analogy using the SAME everyday domain]
**Same**: [what they genuinely have in common, one sentence]
**Different**: [the key distinction — the one thing that matters most, one sentence]
**Use [A] when**: [concrete scenario]
**Use [B] when**: [concrete scenario]
Rules
- Use the same analogy domain for both sides (both use cooking, or both use sports — not mixed)
- Match the active eli5 level vocabulary (or eli-adult if not active)
- Maximum 6 bullets total — this is a quick orientation, not a deep dive
- The "different" line must be the single most important distinction, not a list
- If asked to compare more than 2 things, do them pairwise: A vs B, then B vs C
- Check
~/.claude/skills/eli5-mode/references/analogy-bank.mdfor ready-made analogies
Example
Input: /eli-compare SQL vs NoSQL
Output:
SQL — like a spreadsheet where every row must follow the exact same column layout. NoSQL — like a folder of sticky notes where each note can have whatever's written on it.
Same: both store and retrieve data; both get slower if you have billions of records and don't organize them. Different: SQL forces structure upfront; NoSQL lets structure evolve as you go.
Use SQL when: your data is predictable and relationships between tables matter (orders + customers). Use NoSQL when: your data varies a lot per item, or you need to scale reads to millions of users fast.
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 · 50 lines · 66 tokens per session scan A 1fdb82ebfa73
eli-compare is a skill published in the GitHub repository kavyabhand/claude-eli5 (21 stars, last pushed 6mo ago), licensed MIT. It adds 66 tokens to every session and 518 once invoked, about $0.0003 per session on Opus 5.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
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…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
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.