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/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/explain)<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/explain"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/explain/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/boparaiamrit/skills-by-amrit/explain"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/explain.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.00017 | $0.00349 |
| Opus 5 | $0.00009 | $0.00175 |
| Sonnet 5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
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 9d 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
/explain — Code Explanation
Explain code in a clear, educational way.
Instructions
-
Read the target from
$ARGUMENTS:- Full file or specific function/class
- Understand ALL the code before explaining any of it
-
Structure the explanation:
🎯 One-Sentence Summary
What does this code do in plain English?
🔗 Analogy
Compare it to something from everyday life. E.g.: "This function is like a post office — it receives packages (requests), sorts them by destination (routes), and hands them to the right delivery truck (handler)."
📊 Diagram
Draw an ASCII diagram showing the flow:
Input → [Validate] → [Transform] → [Store] → Output ↓ ↓ [Error] [Notify]🚶 Step-by-Step Walkthrough
Walk through the code line by line:
- First, we... (line X)
- Then... (line Y)
- Finally... (line Z)
⚠️ Gotcha
What's a common mistake or misconception about this code?
🔗 Related Code
What other files/functions does this interact with?
-
Keep it conversational — explain like you're teaching a friend.
-
Highlight the WHY — not just what the code does, but why it's written this way.
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.
- 9d ago First seen · 48 lines · 17 tokens per session scan A 382295539508
explain is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 349 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-08-31.
Other commands, from other repositories
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-13-4.en
Welcome to Lesson 13-4: Landing Page Implementation!
start-0-8
A Japanese-language command that displays the current project setup progress.