microsoft/waza is a Go command-line tool for building and evaluating AI agent skills through test suites, benchmarks, and model comparisons. It is for developers who need to measure and improve how reliably agent skills work. The catalogue entries are Waza's own skills, instructions, agent, and MCP integration.
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 skills add microsoft/waza --skill code-explainergit clone --depth 1 https://github.com/microsoft/wazaWrote 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/microsoft/waza/code-explainer)<a href="https://agentmods.dev/skills/microsoft/waza/code-explainer"><img src="https://agentmods.dev/badge/skills/microsoft/waza/code-explainer/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/microsoft/waza/code-explainer"><img src="https://agentmods.dev/badge/skills/microsoft/waza/code-explainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00135 | $0.01146 |
| Opus 5.5 | $0.00054 | $0.00458 |
| Sonnet 5.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 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 — 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.
- 1mo 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,420 stars, last pushed today), licensed MIT. It adds 135 tokens to every session and 1,146 once invoked, about $0.0005 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…
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…
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.
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.