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 isvlasov/rageatc-oss --skill eli40git clone --depth 1 https://github.com/isvlasov/rageatc-ossWrote 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/isvlasov/rageatc-oss/eli40)<a href="https://agentmods.dev/skills/isvlasov/rageatc-oss/eli40"><img src="https://agentmods.dev/badge/skills/isvlasov/rageatc-oss/eli40/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/isvlasov/rageatc-oss/eli40"><img src="https://agentmods.dev/badge/skills/isvlasov/rageatc-oss/eli40.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.00081 | $0.00360 |
| Opus 5 | $0.00041 | $0.00180 |
| Sonnet 5 | $0.00016 | $0.00072 |
| Haiku 4.5 | $0.00008 | $0.00036 |
Grade A, and why
eli40 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 9d 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
ELI40
Re-explain for an intelligent adult with broad general knowledge but no expert depth in the area being discussed.
Behaviour
Without argument: re-explain your most recent message or suggestion, covering the same ground. With argument (e.g. /eli40 HTMX frontend): explain the given topic from scratch.
- Replace jargon with plain language, or define it inline on first use
- Use analogies to familiar concepts where they genuinely clarify
- Explain the "why" — connect facts to reasons, don't just state them
- Keep the structure — same logical flow, more accessible level
- Be honest about simplification — if glossing over important nuance, say so briefly
Calibration
Assume they understand variables, APIs, databases, git, basic networking, and how the web works. Assume they do NOT know framework-specific internals, protocol details, academic CS terminology, or niche architectural patterns. Concrete examples over abstract definitions; simpler doesn't mean longer.
Don't patronise ("so basically, a computer is like a brain..."), don't pile on caveats, don't turn it into a lecture — roughly match the length of the original explanation, and never lean on "basically" or "simply put" as crutches.
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.
- 9d ago First seen · 25 lines · 81 tokens per session scan A 3734f941f142
eli40 is a skill published in the GitHub repository isvlasov/rageatc-oss (9 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 360 once invoked, about $0.0004 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-31.
Other skills, from other repositories
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
examples
Provide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes, best-practice advice, or audits.
learning-and-development
Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.
top-one-percent
Teach any topic deeply from first principles and build evidence-based paths toward exceptional capability. Use when a user asks to understand, explain, learn, or deep-dive into a topic; asks why or how something works, why it matters, how alternatives compare, or what different perspectives reveal; requests current…
async-learning-teacher
Transform saved links, papers, articles, posts, videos, and reference collections into approachable AI teaching artifacts for later study. Use when a user wants to queue learning material, create a readable explanation from a source, teach a paper or post step by step, or run an interactive tutor that validates…