Borrowing it
Nothing to install: this file belongs to kissrosecicd-hub/agents-evolution. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kissrosecicd-hub/agents-evolution/main/.agents/skills/explain-complex-code/SKILL.mdgit clone --depth 1 https://github.com/kissrosecicd-hub/agents-evolutionWrote 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/kissrosecicd-hub/agents-evolution/explain-complex-code)<a href="https://agentmods.dev/skills/kissrosecicd-hub/agents-evolution/explain-complex-code"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/explain-complex-code/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/kissrosecicd-hub/agents-evolution/explain-complex-code"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/explain-complex-code.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.00041 | $0.00817 |
| Opus 5.5 | $0.00016 | $0.00327 |
| Sonnet 5.5 | $0.00008 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
explain-complex-code 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 1mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explain Complex Code
Навык объяснять сложный код простым языком. Активируется только по запросу пользователя.
Триггеры
Пользователь говорит:
- «объясни [код/функцию/файл/это]»
- «что тут происходит»
- «разбери» / «разложи»
- «explain» / «walk me through»
- «как это работает»
- «не понимаю этот кусок»
- «объясни как новичку»
- «eli5» / «explain like I'm 5»
Формат ответа
Всегда соблюдай структуру:
TL;DR (1-2 строки) → суть без деталей
Аналогия из реального мира → привязка к знакомому
Структура/архитектура → как организовано
Ключевые механизмы → что важно
Поток выполнения → что за чем происходит
Подводные камни → баги, риски, edge cases
Если код короткий — сократи до TL;DR + аналогия + 1 абзац. Если код длинный — добавь все секции.
Правила
Обязательные
- TL;DR всегда первым. 1-2 строки. Без TL;DR — ответ провален.
- Аналогия из реального мира. Не абстрактная. Физический объект, бытовая ситуация, профессия.
- Термин = мгновенное пояснение. Нельзя написать «использует debounce» без «(задержка чтобы не дёргать на каждый чих)».
- Код — в code block. Объяснение — вокруг кода, не внутри.
- Архитектура — диаграмма текстом. Стрелки, отступы, ASCII. Не «ну ты понял».
Запрещённые
- ❌ «Ну это просто...» — для просящего это НЕ просто
- ❌ «Очевидно что...» — ничего не очевидно
- ❌ «Как вы знаете...» — не предполагаешь уровень
- ❌ Ссылка на документацию вместо объяснения
- ❌ Пересказ кода строчка-за-строчкой без контекста ЗАЧЕМ
Уровни детализации
Используй gradual.md когда:
- Пользователь просит «объясни постепенно» / «от простого»
- Код очень сложный (500+ строк, много абстракций)
- Пользователь явно новичок
Используй eli5.md когда:
- Пользователь говорит «объясни как ребёнку» / «eli5» / «на пальцах»
- Нужно убрать весь жаргон
- Объясняешь концепцию, не детали реализации
Используй feynman.md когда:
- Пользователь просит «разбери по шагам» / «как это работает внутри»
- Нужно понять механизм, не просто «что делает»
- Готовишься к собеседованию или code review
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.
- 1mo ago First seen · 84 lines · 41 tokens per session scan A 485cf358a351
explain-complex-code is a skill published in the GitHub repository kissrosecicd-hub/agents-evolution (31 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 817 once invoked, about $0.0002 per session on Opus 5.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-30.
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…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
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
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.