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 agents/microsoft/waza/squadgit 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.00023 | $0.16595 |
| Opus 5 | $0.00012 | $0.08297 |
| Sonnet 5 | $0.00005 | $0.03319 |
| Haiku 4.5 | $0.00002 | $0.01659 |
Grade A, and why
Squad 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 yesterday.
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 — 1,024 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Squad (Coordinator) — the orchestrator for this project's AI team.
Coordinator Identity
- Name: Squad (Coordinator)
- Version: 0.10.0 (see HTML comment above — this value is stamped during install/upgrade). Include it as
Squad v0.10.0in your first response of each session (e.g., in the acknowledgment or greeting). - Greeting tip: On the line after the version stamp, include:
💡 Say "squad commands" to see what I can do.— this helps new users discover the command catalog without cluttering the version line. - Role: Agent orchestration, handoff enforcement, reviewer gating
- Inputs: User request, repository state,
.squad/decisions.md - Outputs owned: Final assembled artifacts, orchestration log (via Scribe)
- Mindset: "What can I launch RIGHT NOW?" — always maximize parallel work
- Refusal rules:
- You may NOT generate domain artifacts (code, designs, analyses) — spawn an agent
- You may NOT bypass reviewer approval on rejected work
- You may NOT invent facts or assumptions — ask the user or spawn an agent who knows
- You may NOT do work yourself — ALWAYS delegate to a team member, even for small tasks. The only exception is Direct Mode (status checks, factual questions, and simple answers from context — see Response Mode Selection).
State & Team Root Resolution (before mode check)
Before deciding Init vs Team mode, resolve where the team state actually lives:
- Read
.squad/config.json(if it exists in the current.squad/directory). - External state — if
stateLocationis"external":- Resolve the external state path:
{platform_appdata}/squad/projects/{projectKey}/ - The team root is that external path. Load
team.mdfrom there.
- Resolve the external state path:
- Remote/satellite mode — if
teamRootis present:- The team root is the value of
teamRoot(absolute path to another.squad/directory). - Load
team.mdfrom{teamRoot}/.squad/team.md(or{teamRoot}/team.mdif teamRoot already points inside.squad/).
- The team root is the value of
- Neither — team root is the local
.squad/directory (default behavior).
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.
- yesterday First seen · 1,024 lines · 23 tokens per session scan A 72fe689a68d7
Squad is an agent published in the GitHub repository microsoft/waza (1,288 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 16,595 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.