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.
Borrowing it
Nothing to install: this file belongs to microsoft/waza. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/waza/main/.github/skills/squad-help/SKILL.mdgit 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/squad-help)<a href="https://agentmods.dev/skills/microsoft/waza/squad-help"><img src="https://agentmods.dev/badge/skills/microsoft/waza/squad-help/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/squad-help"><img src="https://agentmods.dev/badge/skills/microsoft/waza/squad-help.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.00027 | $0.00995 |
| Opus 5.5 | $0.00011 | $0.00398 |
| Sonnet 5.5 | $0.00005 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
squad-help 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 5d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: squad-help
Quick reference. If you're reading this because a user said "use squad" or "squad" or "set up a squad", you're in the right place — read on for the correct invocation paths.
Squad coordinator and squad menu skill
The Squad framework registers a custom Copilot CLI agent at .github/agents/squad.agent.md. The agent is named Squad and its description is "Your AI team. Describe what you're building, get a team of specialists that live in your repo."
Copilot CLI agents and skills are different things:
| Thing | How to invoke | Example |
|---|---|---|
| Menu skill | Host skill tool, natural-language match, or exposed skill command | skill(squad) when available |
| Agent | task tool with agent_type=<name> |
task(name="...", agent_type="Squad", prompt="...") |
| Slash command | Host-dependent built-in command or exposed user-invocable skill | /squad when the host exposes the installed menu |
The Squad agent performs coordination; the separate squad menu skill lives at
.github/skills/squad/SKILL.md and declares user-invocable: true. They are not
interchangeable. Slash-command availability is host-dependent: use /squad only
where the host exposes that skill as a command. Otherwise use its natural-language
triggers or the host's skill picker/tool, when available; invoke the coordinator agent
for actual orchestration.
How to actually use Squad
Pick the path that matches the user's intent:
A) Invoke the Squad coordinator agent (most common)
The Squad coordinator orchestrates a team of specialists. It routes work to the right agent, scaffolds a team if none exists, and enforces handoffs.
task(
name="<short-task-name>",
agent_type="Squad",
prompt="<what you want the team to do>"
)
Use this when the user says things like:
- "Use Squad to build X"
- "Set up an AI team for this project"
- "Have the Squad coordinator design Y"
- "Spawn Squad" / "Squad, help me with ..."
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.
- 5d ago First seen · 105 lines · 27 tokens per session scan A 35cb2e9b8634
squad-help is a skill published in the GitHub repository microsoft/waza (1,424 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 995 once invoked, about $0.0001 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-10-17.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…