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/jaichangpark/workshop-harness/eli5npx skills add JAICHANGPARK/workshop-harness --skill eli5git clone --depth 1 https://github.com/JAICHANGPARK/workshop-harnessWrote 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/jaichangpark/workshop-harness/eli5)<a href="https://agentmods.dev/skills/jaichangpark/workshop-harness/eli5"><img src="https://agentmods.dev/badge/skills/jaichangpark/workshop-harness/eli5.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 | $0.00042 | $0.00532 |
| Opus 5 | $0.00021 | $0.00266 |
| Sonnet 5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
eli5 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ELI5 (Explain Like I'm 5) Skill
Based on the Claude Code Community Plugin specification (
eli5@claude-community).
Purpose
Explains complex technical topics, code modules, design trade-offs, and runtime errors in dead-simple terms as if explaining to a 5-year-old child. Focuses on intuitive real-world analogies, visual diagrams, and minimal text rather than dense jargon.
Core Rules
-
Big Pictures & Visuals First:
- Always illustrate the explanation with clean diagrams (Mermaid flowcharts/mindmaps or visual artifacts).
- Use visual components (boxes, arrows, illustrations) rather than long paragraphs of text.
-
No Technical Jargon:
- Strip away math formulas, acronyms, and low-level implementation details.
- Ground every concept in a physical, everyday object (e.g. toy box, library, kitchen, telephone, mail carrier).
-
Very Few Words:
- Keep sentences short, conversational, and direct.
- Avoid walls of text. Use bullet points and callouts.
-
Preserve the Core Mechanism:
- Simplicity must never sacrifice accuracy. The explanation must correctly represent the fundamental cause-and-effect relationship under the hood.
Output Structure
When the user asks to explain a concept or runs /eli5 <topic>:
1. The 1-Sentence Analogy
A single sentence comparing the concept to something from daily life.
2. The Visual Picture (Mermaid Diagram)
A simple, colorful flowchart showing how the parts interact.
flowchart LR
A["Everyday Thing 1"] --> B["Action / Bridge"] --> C["Result / Output"]
3. Step-by-Step Story (3 Simple Steps)
- Step 1: Where it starts (e.g. "You ask for a toy").
- Step 2: What happens behind the scenes (e.g. "The helper robot goes to the closet").
- Step 3: What you get back (e.g. "The robot hands you the toy").
4. What this means in your code / system
A brief 1-2 sentence bridge connecting the analogy back to the user's actual project or terminal error.
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.
- 4d ago First seen · 57 lines · 42 tokens per session scan A 4daf644887f0
eli5 is a skill published in the GitHub repository JAICHANGPARK/workshop-harness (5 stars, last pushed 3d ago), licensed MIT. It adds 42 tokens to every session and 532 once invoked, about $0.0002 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
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…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
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
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
best-practices
Searchable knowledge base of 152+ programming best practices across 30+ languages and frameworks. BM25-powered search over curated resources from industry leaders (Google, Airbnb, Uber, Mozilla, Shopify, OWASP).