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.
git clone --depth 1 https://github.com/Amey-Thakur/AI-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/commands/amey-thakur/ai-skills/explain-code)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/explain-code"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/explain-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/commands/amey-thakur/ai-skills/explain-code"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/explain-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.00021 | $0.00302 |
| Opus 5 | $0.00010 | $0.00151 |
| Sonnet 5 | $0.00004 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
explain-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 6d 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.
What it actually says
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
Explain the code below to a reader who is {level}.
Structure:
- One sentence: what this code accomplishes for its caller.
- The walk-through: follow the execution order (not the line order), explaining each meaningful step in plain language. Name the technique when one is used (memoization, debounce, two-phase locking) and say why it is here.
- The sharp edges: inputs or states where this code fails, surprises, or performs badly: only real ones you can point to in the code.
- Questions the code raises: anything that looks intentional but undocumented (a magic number, a swallowed error). Phrase as questions, not accusations.
Rules:
- Explain only the code given; if it references things not shown, say what you can infer and mark it as inference.
- No rewriting or reviewing unless asked: this is comprehension, not critique.
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.
- 6d ago First seen · 39 lines · 21 tokens per session scan A e00342f32a9e
explain-code is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (7 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 302 once invoked, about $0.0001 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-03.
Other commands, from other repositories
debug-issue
Hypothesis-driven debugging with runtime evidence — Sentry, Firecrawl, and Sequential Thinking, not guessing.
error-plan
Error-handling & observability audit (Sentry + Langfuse) — plan only, no fixes until approved.
stub-plan
Stub / dead-link / fake-component audit + wiring plan — no fixes until approved.
fit-check
Audit a design or subsystem for primitive/problem fit (the wrong-primitive trap). Runs the architecture-fit-check skill.
perf-audit
Profile a performance complaint and fix the biggest contributor with Instruments and MetricKit.
swift6-fix
Diagnose and fix Swift 6 strict concurrency, Sendable, or MainActor isolation errors.