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/kirodotdev/kirocrew/explain-fornpx skills add kirodotdev/KiroCrew --skill explain-forgit clone --depth 1 https://github.com/kirodotdev/KiroCrewWrote 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/kirodotdev/kirocrew/explain-for)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/explain-for"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/explain-for.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.00102 | $0.03257 |
| Opus 5 | $0.00051 | $0.01629 |
| Sonnet 5 | $0.00020 | $0.00651 |
| Haiku 4.5 | $0.00010 | $0.00326 |
Grade A, and why
explain-for 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 yesterday.
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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
explain-for — write it for one named audience
One explanation cannot serve everyone. This skill makes you name the audience first, verify the facts second, and only then write.
Step 0 — check that this is actually an audience request
Trigger matching here is word-overlap against the phrases above, so it is probabilistic and it will sometimes fire on a request that merely contains the word "explain". Before entering the skill, confirm the user wants an explanation pitched at somebody. If they just want to know why CI failed, answer that question normally and ignore everything below.
Step 1 — resolve the audience
Pick exactly one audience.
Check memory before guessing. Crew carries a persistent user profile, and a request like "explain this to my daughter" or "break this down for Priya" often resolves against something already recorded — an age, a role, an interest. Search memory and lessons for that person and use what is there; guessing an age the profile already contradicts is the most visible way this skill fails.
If nothing resolves and no audience is named, do not silently invent one:
- Explicit smallest-audience phrasing ("dumb it down", "explain like I am") means Age 5. That is the request.
- Anything else with no audience — ask which audience in one line, or state the row you assumed in one clause so the user can correct it.
If the request names someone you cannot classify (a specific colleague, a title absent from the tables), map them onto the nearest row and say which row.
Ages
| Audience | Calibration |
|---|---|
| Age 5 | Smallest words. Analogies from toys, animals, candy, playground. One idea per sentence. |
| Age 10 | Elementary. Cause-and-effect is fine. Analogies from school, sports, video games. |
| Age 15 | Some abstraction is fine. Analogies from phones, games, social apps. Casual, never try-hard. |
| Age 20-30 | Direct and clear. Analogies from work, money, daily logistics. |
| Age 40+ | Respectful, unhurried. Analogies from home ownership, career, running a household. |
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.
- yesterday First seen · 263 lines · 102 tokens per session scan A 78359d37b7a9
explain-for is a skill published in the GitHub repository kirodotdev/KiroCrew (3,532 stars, last pushed 2d ago), licensed Apache-2.0. It adds 102 tokens to every session and 3,257 once invoked, about $0.0005 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-09-02.
Other skills, from other repositories
edu-math-tutorial
数学题分步讲解视频的领域知识。适用场景：(1) 用户给出一道数学题并要求做讲解/ 解题视频；(2) 用户说"讲解这道题"、"生成解题视频"、"make a math tutorial"； (3) 需要中文数学教学视频，涉及方程、公式或几何图形。本 skill 只提供领域 知识（题目拆解、讲解节奏、旁白文案规范、版式与 KaTeX 排版风格）；画面、 配音与成片一律用 Creator 原生 Element 与工具从源头构建。.
scientific-critical-thinking
Evaluate scientific claims and evidence quality. Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis. Best for understanding evidence quality, identifying flaws. For formal peer review…
self-improve-with-tinyfish
Enables Hermes to create new reusable skills for itself by researching live web sources with TinyFish Search and Fetch, analyzing source coverage, writing SKILL.md files, and installing them into Hermes memory. Use when the user asks Hermes to learn, teach itself, upgrade itself, or save a reusable capability.
office-pptx
Use when the user asks to create, inspect, verify, polish, or deliver PowerPoint .pptx decks, Google Slides-targeted deck artifacts, strategy narratives, operating reviews, pitch decks, teaching decks, section slides, bullet slides, or source-to-PPTX transformations.
omh-curriculum-design
This is a Hermes-native curriculum-design workflow skill.
flashcards
Spaced repetition flashcard system for learning. SM-2 algorithm, supports text and cloze deletion cards.