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 sergeyklay/.agents --skill explain-itgit clone --depth 1 https://github.com/sergeyklay/.agentsWrote 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/sergeyklay/.agents/explain-it)<a href="https://agentmods.dev/skills/sergeyklay/.agents/explain-it"><img src="https://agentmods.dev/badge/skills/sergeyklay/.agents/explain-it.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.1 | $0.00188 | $0.03612 |
| Opus 5 | $0.00094 | $0.01806 |
| Sonnet 5 | $0.00038 | $0.00722 |
| Haiku 4.5 | $0.00019 | $0.00361 |
Grade A, and why
explain-it 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explaining Technical Concepts
Construct understanding, do not transfer information. The reader is a technical professional who is unfamiliar with this specific topic, not with technical work in general. They can handle complexity. They have not encountered this particular thing yet.
The job is to be the colleague who spent a week studying the thing and now explains what they found - directly, with the relevant intermediate steps visible, without showing off, and without condescension.
The Two Non-Negotiables
Two rules apply to every output produced under this skill. Failing either one is a defect, regardless of how good the rest of the explanation is.
Language rule
Always respond in the language the question was asked in. Chinese question → Chinese response. English → English. Russian → Russian. No exceptions, no mixing.
Code examples, API names, function signatures, command flags, and protocol identifiers stay in their original technical form. All prose, structure, headers, and explanation must be in the question's language.
Honesty rule
Do not state implementation details that have not been verified. If a fact came from training data and was not confirmed against source code or authoritative documentation, mark it as such or omit it. False confidence corrupts mental models in ways that are hard to undo later.
When sources conflict, report the conflict. A discrepancy between documentation and source code is itself important information.
When completeness and certainty clash - the reader needs a detail you have not verified - certainty wins. Give less, and mark the gap. A fluent, complete explanation that is wrong corrupts the reader's model worse than an honest hole does.
The four maxims behind every rule
Every rule below is downstream of one idea: an explanation is a cooperative act, and the reader assumes you are cooperating. Grice's four maxims name what that assumption covers, Quantity, Quality, Relation and Manner, and Quality wins whenever it clashes with the other three (see the Honesty rule). Each is defined in references/anti-patterns.md; read them when something reads badly and you cannot name why.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -29 lines fac6048dce09
- 4d ago Changed aaa8d0495b7f
- 8d ago First seen · 179 lines · 188 tokens per session scan A 371e3eea03cb
explain-it is a skill published in the GitHub repository sergeyklay/.agents (5 stars, last pushed today), licensed Apache-2.0. It adds 188 tokens to every session and 3,612 once invoked, about $0.0009 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
ai-education-data-explorer
An education-data analysis helper for interpreting teaching or recruitment data. It turns supplied data into a diagnosis, improvement suggestions, and scoring or activity checklists.
ai-educational-research-methods
An education-research methods review helper for checking whether a study uses a suitable research method. It creates teaching or hiring feedback, improvement suggestions, and checklists from supplied material.
ai-upskilling-training-diagnosis
A business-diagnosis assistant that turns provided information into a summary, findings, and recommended actions.
course-landing-page-conversion-review
A conversion experiment review assistant for evaluating changes to an online course landing page. A landing page is a focused web page designed to persuade visitors to take an action, such as enrolling.
course-outline-market-positioning
A business diagnosis assistant for evaluating course ideas and their market positioning using supplied information.
lesson-plan-activity-designer
An activity-design assistant for creating or reviewing learning activities. The available description identifies it as a visual-quality diagnosis tool, so its exact activity-design capabilities are not fully specified.