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-commitnpx skills add kavyabhand/claude-eli5 --skill eli-commitgit clone --depth 1 https://github.com/kavyabhand/claude-eli5What 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 | $0.00059 | $0.00433 |
| Opus 5 | $0.00030 | $0.00217 |
| Sonnet 5 | $0.00012 | $0.00087 |
| Haiku 4.5 | $0.00006 | $0.00043 |
Grade A, and why
eli-commit 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 2d 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-COMMIT — Plain-Language Commit Message
Reads staged changes and writes a commit message that explains the why, not just the what.
Steps
1. Read staged changes
git diff --cached 2>/dev/null
If nothing staged, also try:
git diff HEAD~1..HEAD 2>/dev/null
2. Write the commit message
Subject line (required, ≤ 72 chars):
- Starts with a verb: Add, Fix, Remove, Update, Simplify
- Answers "what and why" in plain language
- No jargon in the subject — if a technical term is unavoidable, follow with a plain equivalent
Body (optional, use when the why isn't obvious):
- 2–4 bullet points
- Focus on why this change was made, not what files changed (the diff shows that)
- Plain language — a teammate who joined yesterday should understand
Rules
- If the diff is empty, ask the user to describe the change
- Use conventional commit format ONLY if the project already uses it (check existing commits)
- Never summarize the diff literally ("changed line 42 of auth.js") — explain the reason
- Short, clear subject line beats a long, jargon-heavy one every time
Example
Staged change: adds retry logic to API calls
Output:
Add automatic retry when the server is temporarily unavailable
- Without this, a single slow moment would fail the whole request for the user
- Now we try up to 3 times with a short pause between attempts
- No change to the user-facing experience — this is invisible when it works
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.
- 2d ago First seen · 55 lines · 59 tokens per session scan A 3d1d5ee90ab4
eli-commit 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 433 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
commit
Commit message formatting and guidelines.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
keploy-pr-workflow
Guide for creating PRs and issues on keploy repositories — PR format, customer-data hygiene, commit conventions, sign-off. Invoke when the user asks to open, update, or review a pull request or issue, when preparing a commit that will land in main, or whenever a change is about to leave the local machine.
git-commit
Generate well-formatted git commit messages following conventional commit standards.