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/cooltheworld/evolution-skills/two-layer-explainnpx skills add coolTheWorld/evolution-skills --skill two-layer-explaingit clone --depth 1 https://github.com/coolTheWorld/evolution-skillsWrote 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/cooltheworld/evolution-skills/two-layer-explain)<a href="https://agentmods.dev/skills/cooltheworld/evolution-skills/two-layer-explain"><img src="https://agentmods.dev/badge/skills/cooltheworld/evolution-skills/two-layer-explain.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.00036 | $0.01200 |
| Opus 5 | $0.00018 | $0.00600 |
| Sonnet 5 | $0.00007 | $0.00240 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
two-layer-explain 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 3d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
"Explain it like I'm five" leaves a reader at I think I get it: the analogy sticks and the mechanism stays a blur. Explain twice instead — once so a newcomer can follow, once so an expert would sign it — then bridge the two, because the gap between the layers is where a misconception lives.
Write in the language the user writes in.
1. Pin the concept
The user names a concept or asks a question. Explain a concept as named. Answer a question: each layer answers it in its own register, through the concept or concepts the answer turns on, so the user leaves with the answer and not only with the background. If there is no argument, or too little to tell what is to be explained, ask one question for it and stop.
Before writing either layer, hold the mechanism in one sentence: what happens, in what order, and what it depends on — for a question, the mechanism its answer rests on. Both layers deliver that sentence; a layer 1 written without it becomes an analogy of the wrong thing.
Done when the input is pinned as a concept to explain or a question to answer, and its mechanism is written as a single causal sentence you will hold both layers to.
2. Explain for the newcomer
Write layer 1 in everyday language, for a reader with no background at all, around one concrete example.
Pick the example so it runs the mechanism rather than illustrating the name: a specific situation with actors and a sequence, walked through start to finish, so the reader watches the thing happen. Choose an analogy whose parts each stand for a part of the mechanism, so layer 2 can refine it instead of replacing it; an analogy that carries only the feel of the concept breaks at the misconception, and step 4 will have to disown it.
Done when every sentence can be followed by a reader with no background, the one example is concrete and walked through start to finish, and each part of the analogy stands for a named part of the mechanism.
3. Explain for the expert
Write layer 2 in the field's precise terminology, covering the core mechanism, the boundaries of applicability, and the common misconceptions.
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.
- 3d ago First seen · 58 lines · 36 tokens per session scan A d29285e6b80f
two-layer-explain is a skill published in the GitHub repository coolTheWorld/evolution-skills (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,200 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
skill-creator
Create or improve Zhin Agent skills (SKILL.md). Use when asked to add a skill, write SKILL.md, document a repeatable agent workflow, or refine skill frontmatter/keywords. Triggers: 创建技能, 写 SKILL, skill-creator, 加 skill.
webman
Expert skill for the webman framework (a long-lived, in-memory PHP framework based on workerman). Covers routing, controllers, middleware, database/Redis, custom processes, timers, coroutines (v2), plugin development, and guarding against memory leaks and cross-request state pollution under the resident process model.…
clawallex-skill
Pay for anything with USDC — virtual cards for any online checkout.
building-edgespark-apps
Build and modify EdgeSpark apps. Use when a project has edgespark.toml, the user mentions EdgeSpark, or work involves the edgespark CLI, server SDK types, storage/auth/database workflows, deployment, or @edgespark/web.
edgespark-frontend-design
Design and redesign EdgeSpark frontends with distinctive, production-grade visual direction instead of generic AI-looking UI. Use when building or polishing landing pages, marketing sites, dashboards, auth flows, portfolios, product surfaces, or reusable frontend sections in EdgeSpark, especially when the task…
video-to-guide
Transforms YouTube videos into full, structured written guides — every detail preserved, no summarizing. Use when the user wants to turn a video into a guide, study notes, learning material, or any written format that captures the full depth of the content. The skill fetches the transcript automatically and produces…