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-recapgit 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-recap)<a href="https://agentmods.dev/skills/kavyabhand/claude-eli5/eli-recap"><img src="https://agentmods.dev/badge/skills/kavyabhand/claude-eli5/eli-recap.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.00062 | $0.00569 |
| Opus 5 | $0.00031 | $0.00284 |
| Sonnet 5 | $0.00012 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
eli-recap 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 8d 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-RECAP — Session Digest + Cross-Session Memory
Produces a structured digest of this session and saves a concept index for future reference.
Format
## What we covered
- **[Concept]** — [one plain-language sentence summary]
- **[Concept]** — [one plain-language sentence summary]
[Group by topic if multiple topics came up]
## Key analogies that stuck
- [Concept]: [the analogy]
- [Concept]: [the analogy]
[Best 3–5 only]
## Open questions
[Anything that came up but wasn't fully explained — or "None — good coverage!"]
---
*Level: [active eli5 level] · Session: [today's date]*
Save concept index (cross-session memory)
After producing the recap, save a concept index so future sessions can build on this one:
node -e "
const fs = require('fs');
const f = '.claude/eli5-concepts.json';
let c = {};
try { c = JSON.parse(fs.readFileSync(f, 'utf8')); } catch {}
const today = new Date().toISOString().split('T')[0];
// Concepts are extracted from the session summary above
if (!c.sessions) c.sessions = [];
c.sessions.push({ date: today, count: 0 }); // updated by the skill with actual concepts
fs.writeFileSync(f, JSON.stringify(c, null, 2));
" 2>/dev/null || true
Write the actual concept list (extracted from your session recap) to .claude/eli5-concepts.json:
{
"sessions": [
{
"date": "YYYY-MM-DD",
"level": "eli-adult",
"concepts": ["concept1", "concept2", "concept3"]
}
]
}
Rules
- If nothing has been explained in this session: "Nothing yet — ask me anything and I'll explain it at your level!"
- Keep concept summaries to one sentence — this is a reference, not a re-explanation
- After the recap, always offer: "Type /eli-save to export this to
eli5-notes.md" - Also offer: "Type /eli-quiz to test yourself on what we covered"
- Match the eli5 level that was active for most of the session
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.
- 8d ago First seen · 72 lines · 62 tokens per session scan A c810974c3278
eli-recap is a skill published in the GitHub repository kavyabhand/claude-eli5 (21 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 569 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.