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/avinashp/agentsatlas/explaining-codenpx skills add AvinashP/AgentsAtlas --skill explaining-codegit clone --depth 1 https://github.com/AvinashP/AgentsAtlasWhat 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.00035 | $0.01346 |
| Opus 5 | $0.00017 | $0.00673 |
| Sonnet 5 | $0.00007 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
explaining-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 2d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explaining Code Skill
Explain code clearly using multiple techniques for different learning styles.
Workflow
1. Understand the Context
Before explaining, understand:
- What is the user's knowledge level?
- What specifically do they want to understand?
- What's the scope? (single function, module, system)
2. Choose Explanation Strategy
| If they ask... | Start with... |
|---|---|
| "How does X work?" | High-level flow, then details |
| "What does this code do?" | Purpose, then step-by-step |
| "Why is it written this way?" | Problem it solves, alternatives |
| "I'm confused about..." | Clarify specific concept |
3. Build the Explanation
Layer your explanation:
- One sentence summary - What is the core purpose?
- Analogy - Relate to something familiar
- Visual diagram - Show structure/flow
- Walk through - Step by step with code
- Key concepts - Highlight important patterns
4. Use Multiple Representations
Different people learn differently:
- Visual learners: Diagrams, flowcharts
- Sequential learners: Step-by-step walkthrough
- Conceptual learners: Analogies, mental models
- Hands-on learners: Example usage, experiments to try
Explanation Techniques
The Zoom Technique
Start wide, then zoom in:
System Level: "This app handles user authentication"
↓
Module Level: "This module manages sessions"
↓
Function Level: "This function validates tokens"
↓
Line Level: "This line checks expiration"
The Analogy Technique
Connect to familiar concepts:
| Code Concept | Real-world Analogy |
|---|---|
| API | Restaurant menu + waiter |
| Cache | Sticky notes on your desk |
| Database | Filing cabinet |
| Queue | Line at a store |
| Stack | Stack of plates |
| Hash table | Library index cards |
| Middleware | Security checkpoint |
| Event loop | Receptionist handling calls |
| Promise | IOU note |
| Closure | Backpack carrying supplies |
What ships with it
1 file 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.
- 2d ago First seen · 205 lines · 35 tokens per session scan A 7caa21ce05c8
explaining-code is a skill published in the GitHub repository AvinashP/AgentsAtlas (7 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 1,346 once invoked, about $0.0002 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
orchestrator-main
多智能体工作流的主调度智能体核心逻辑（平台无关）。定义状态机管理、子 Agent 调度接口、进度追踪和回退决策。平台适配层负责实现具体的调度方式。.
learn-mcp
Focused interactive tutor for the Model Context Protocol (MCP) path in AI Engineering from Scratch. Start or resume this route when a learner wants to build, secure, debug, verify, or operate MCP clients, servers, transports, gateways, registries, or conformance gates. Teaches one lesson per invocation and records…
find-your-level
Interactive quiz that maps your AI/ML knowledge to a starting point in the 523-lesson, 20-phase AI Engineering from Scratch curriculum. Trigger phrases: "where should I start", "find my level", "what do I know", "which phase", "assess my knowledge", "placement test", "skip ahead".
learn-agent-skills
Focused interactive tutor for the Agent Skills Engineering path in AI Engineering from Scratch. Start or resume this route when a learner wants to create, discover, invoke, secure, evaluate, package, or port Agent Skills. Teaches one lesson per invocation and records evidence in AGENT-SKILLS-LEARNING.md.
start-learning
One-time onboarding for the AI Engineering from Scratch curriculum (523 lessons, 20 phases). Interviews the learner, runs the placement quiz, and writes LEARNING.md, a persistent study plan the learn skill drives. Trigger phrases: "start learning", "set up the course", "begin the curriculum", "onboard me", "create my…
playwright
Use when the task requires capturing or automating a real browser from the terminal.