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-prgit 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-pr)<a href="https://agentmods.dev/skills/kavyabhand/claude-eli5/eli-pr"><img src="https://agentmods.dev/badge/skills/kavyabhand/claude-eli5/eli-pr.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.00059 | $0.00447 |
| Opus 5 | $0.00030 | $0.00224 |
| Sonnet 5 | $0.00012 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade B, and why
eli-pr 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 7d 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 "{}" What it actually says
ELI-PR — Plain-Language PR Description
Reads the current git diff and writes a PR description a non-engineer can understand.
Steps
1. Get the diff
git diff main...HEAD 2>/dev/null || git diff master...HEAD 2>/dev/null || git diff HEAD~1..HEAD 2>/dev/null || git diff --cached
Also scan recent commit messages:
git log --oneline -10 2>/dev/null
2. Check active eli5 level
cat .claude/eli5-state.json 2>/dev/null || echo "{}"
Default to eli-adult if no level is active.
3. Write the PR description
Use exactly this structure:
## What changed
[One sentence. Plain English. What was built, fixed, or removed — not how.]
## Why
[One sentence. The user/business reason. What problem does this solve?]
## How to test
- [Step 1 — anyone can follow this]
- [Step 2]
- [Step 3 if needed]
## Risk
[One sentence. What could break? Or: "Low risk — no user-facing changes."]
Rules
- Audience: your manager, a designer, a PM — intelligent but not technical
- No jargon without an inline plain-language equivalent (e.g. "cache (temporary storage)")
- The "What changed" line must pass the pub test: could you say it to a friend?
- If the diff is empty or unreadable, ask the user to describe the change
- If eli5-mode is active at a specific level, match that level's vocabulary
- Never invent functionality — only describe what the diff shows
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.
- 7d ago First seen · 60 lines · 59 tokens per session scan B e070986b2131
eli-pr is a skill published in the GitHub repository kavyabhand/claude-eli5 (21 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 447 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".