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/microsoft/waza/code-explainernpx skills add microsoft/waza --skill code-explainergit clone --depth 1 https://github.com/microsoft/wazaWhat 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.00135 | $0.01146 |
| Opus 5 | $0.00068 | $0.00573 |
| Sonnet 5 | $0.00027 | $0.00229 |
| Haiku 4.5 | $0.00014 | $0.00115 |
Grade A, and why
code-explainer 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 3d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Explainer
A skill that explains code snippets in clear, educational language. Helps developers understand unfamiliar code, algorithms, and programming patterns.
Skill Activation Triggers
Use this skill immediately when the user asks to:
- "Explain this code"
- "What does this function do?"
- "Break down this algorithm"
- "Help me understand this snippet"
- "Walk me through this code"
- "What's happening in this file?"
Key Indicators:
- User shares a code snippet and asks for explanation
- User is confused about existing code
- User wants to learn how something works
- User asks "what does X do?" about code
Do NOT use when:
- User wants to write new code
- User wants to fix a bug
- User wants code review with suggestions
- User wants refactoring recommendations
Quick Reference
| Property | Value |
|---|---|
| Input | Code snippet + optional language hint |
| Output | Plain language explanation |
| Best for | Learning, onboarding, code comprehension |
Explanation Guidelines
Structure
A good code explanation should include:
- Overview - One sentence summary of what the code does
- Step-by-step breakdown - Walk through the logic
- Key concepts - Explain any patterns or techniques used
- Example - Show sample input/output if applicable
Tone
- Educational and approachable
- Avoid jargon unless explaining it
- Use analogies when helpful
- Assume the reader is smart but unfamiliar with this specific code
Language-Specific Tips
| Language | Focus On |
|---|---|
| Python | List comprehensions, decorators, generators |
| JavaScript | Async/await, closures, callbacks |
| SQL | JOINs, subqueries, aggregations |
| Java | OOP patterns, generics, streams |
Examples
Example 1: Python Recursion
User prompt:
Explain this code:
```python
def factorial(n):
if n <= 1:
return 1
return n * factorial(n - 1)
Good response:
This is a recursive function that calculates the factorial of a number.
Overview: It multiplies a number by all positive integers less than it (e.g., 5! = 5 × 4 × 3 × 2 × 1 = 120).
Step by step:
- Base case (
if n <= 1): If n is 0 or 1, return 1 (since 0! and 1! both equal 1)- Recursive case: Otherwise, multiply n by factorial(n-1)
Example:
factorial(4)→ 4 × factorial(3) → 4 × 3 × factorial(2) → 4 × 3 × 2 × factorial(1) → 4 × 3 × 2 × 1 = 24
Example 2: JavaScript Async/Await
User prompt:
What does this code do?
```javascript
async function fetchUserData(userId) {
try {
const response = await fetch(`/api/users/${userId}`);
if (!response.ok) throw new Error('User not found');
return await response.json();
} catch (error) {
console.error('Failed:', error);
return null;
}
}
What ships with it
12 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.
- eval.yaml 1.7 KB
- fixtures/factorial.py 82 B runs code
- fixtures/fetch_user.js 313 B runs code
- fixtures/squares.py 49 B runs code
- fixtures/user_orders.sql 147 B
- graders/explanation_quality.py 5.5 KB runs code
- README.md 3.7 KB
- tasks/explain-js-async.yaml 951 B
- tasks/explain-list-comprehension.yaml 1010 B
- tasks/explain-python-recursion.yaml 1.0 KB
- tasks/explain-sql-join.yaml 925 B
- trigger_tests.yaml 2.1 KB
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.
- 3d ago First seen · 145 lines · 135 tokens per session scan A 8b01f2320b06
code-explainer is a skill published in the GitHub repository microsoft/waza (1,288 stars, last pushed 4d ago), licensed MIT. It adds 135 tokens to every session and 1,146 once invoked, about $0.0007 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-30.
Other skills, from other repositories
trulens-notebook-execution
Execute and display Jupyter notebooks for TruLens demos and quickstarts.
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
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
master-yinguang
Use when user asks about 印光大师, 净土, 念佛, 持名念佛, 十念法, 摄耳谛听, 老实念佛, 信愿行, 带业往生, 仗佛慈力, 自力他力, 竖出横超, 往生, 极乐, 阿弥陀佛, 净土三经, 敦伦尽分, 闲邪存诚, 因果报应, 文钞, 一函遍复, or wants teaching in 印光大师 Yinguang's voice. Triggers include "印光"、"文钞"、"老实念佛"、"信愿行"、"带业往生"、"仗佛慈力"、"横超竖出"、"都摄六根"、"净念相继"、"敦伦尽分"、"闲邪存诚"、"因果"、"十念法"、"摄耳谛听"、"一函遍复"、"净土三经"、"往生" — invoke…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
obsidian-to-clew-import
Convert an Obsidian vault or wiki-linked markdown graph into a validated structured-learning graph package for Clew. Use when the user wants to inspect a vault, preview whether it imports cleanly, preserve explicit relation markers, choose only the few import settings that matter, and produce a fail-closed package…