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/coordinator-source-of-truth/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/coordinator-source-of-truth)<a href="https://agentmods.dev/skills/microsoft/waza/coordinator-source-of-truth"><img src="https://agentmods.dev/badge/skills/microsoft/waza/coordinator-source-of-truth/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/coordinator-source-of-truth"><img src="https://agentmods.dev/badge/skills/microsoft/waza/coordinator-source-of-truth.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.00086 | $0.01727 |
| Opus 5.5 | $0.00034 | $0.00691 |
| Sonnet 5.5 | $0.00017 | $0.00345 |
| Haiku 4.5 | $0.00009 | $0.00173 |
Grade A, and why
coordinator-source-of-truth 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load this skill when: the coordinator (or any agent) needs to resolve a "where does this state belong?" or "who is allowed to write this file?" question — e.g., when about to write
.squad/decisions.md, when reviewing whether an agent broke the append-only rule, when answering a user question about Squad's file layout, or when adjudicating a conflict between two files. The short summary insquad.agent.mdis for routing; this skill is the full reference.
State backend note
Files below marked as "Derived / append-only" are mutable state — agents access them with runtime state tools (squad_state_read, squad_state_write, squad_state_append, squad_state_delete, squad_state_list). The runtime decides whether the configured backend stores them on disk, git-native state, or an external provider. Files marked as "Authoritative" are static config and always live on disk regardless of backend.
File hierarchy
Waza support-review override (Squad only): Charter output/persistence restrictions take precedence over generic history, audit-trail or decision-inbox write permissions below. Rai and Fact Checker return findings in the current review response. Only an authorized coordinator or Scribe handles required persistence under the current state contract; no routine review logging is required. Preserve existing historical records. Scribe remains bound by its charter: a decision-only Scribe cannot write logs, histories or audit trails. The Coordinator arranges any required non-decision persistence through an authorized writer; a missing writer is a blocker, not permission for Scribe. These coordination rules do not apply to ordinary Copilot work.
| File | Status | Who May Write | Who May Read |
|---|---|---|---|
.github/agents/squad.agent.md |
Authoritative governance. All roles, handoffs, gates, and enforcement rules. | Repo maintainer (human) | Squad (Coordinator) |
.squad/decisions.md |
Authoritative decision ledger. Single canonical location for scope, architecture, and process decisions. | Coordinator or coordinator-delegated Scribe; already-accepted decisions only, append only | All agents |
.squad/team.md |
Authoritative roster. Current team composition. | Squad (Coordinator) | All agents |
.squad/routing.md |
Authoritative routing. Work assignment rules. | Squad (Coordinator) | Squad (Coordinator) |
.squad/ceremonies.md |
Authoritative ceremony config. Definitions, triggers, and participants for team ceremonies. | Squad (Coordinator) | Squad (Coordinator), Facilitator agent (read-only at ceremony time) |
.squad/casting/policy.json |
Authoritative casting config. Universe allowlist and capacity. | Squad (Coordinator) | Squad (Coordinator) |
.squad/casting/registry.json |
Authoritative name registry; paired transaction. Persistent agent-to-name mappings. | Squad (Coordinator), only via .squad/casting-transactions.md's locked SDK writer |
Squad (Coordinator), paired read |
.squad/casting/history.json |
Derived / append-only contents; paired transaction. Universe usage history and assignment snapshots. | Squad (Coordinator), only via the same paired writer | Squad (Coordinator), paired read |
.squad/casting/registry-history.commit.json |
SDK-owned transaction/hash manifest. Never hand-edit or discard to bypass validation. | Locked SDK paired writer only | SDK paired reader |
.squad/agents/{name}/charter.md |
Authoritative agent identity. Per-agent role and boundaries. | Squad (Coordinator) at creation; agent may not self-modify | Squad (Coordinator) reads to inline at spawn; owning agent receives via prompt |
.squad/agents/{name}/history.md |
Derived / append-only. Personal learnings. Never authoritative for enforcement. | Owning agent only where charter permits; authorized Scribe for required context | Owning agent only |
.squad/agents/{name}/history-archive.md |
Derived / append-only. Archived history entries. Preserved for reference. | Scribe | Owning agent (read-only) |
.squad/orchestration-log/ |
Derived / append-only. Agent routing evidence. Never edited after write. | Scribe | All agents (read-only) |
.squad/log/ |
Derived / append-only. Session logs. Diagnostic archive. Never edited after write. | Scribe | All agents (read-only) |
.squad/templates/ |
Reference. Format guides for runtime files. Not authoritative for enforcement. | Squad (Coordinator) at init | Squad (Coordinator) |
.squad/rai/policy.md |
Authoritative RAI policy. Check categories, terminology standards, and opt-out rules. | Squad (Coordinator) at init or authorized policy changes; Rai read-only | Rai, All agents (read-only) |
.squad/rai/audit-trail.md |
Derived / append-only. Preserve existing redacted records; never raw secrets or harmful content; no routine reviewer logging. | Authorized Coordinator/Scribe only when the current state contract requires persistence | Rai, Squad (Coordinator) |
.squad/fact-checker/policy.md |
Authoritative verification + Devil's Advocate policy. Confidence rating taxonomy, hard anti-fabrication rules, mode triggers, opt-out model. | Squad (Coordinator) at init or authorized policy changes; Fact Checker read-only | Fact Checker, All agents (read-only) |
.squad/fact-checker/audit-trail.md |
Derived / append-only. Preserve existing succinct verdict/citation records, never raw source material; no routine reviewer logging. | Authorized Coordinator/Scribe only when the current state contract requires persistence | Fact Checker, Squad (Coordinator) |
.squad/plugins/marketplaces.json |
Authoritative plugin config. Registered marketplace sources. | Squad CLI (squad plugin marketplace) |
Squad (Coordinator) |
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 · 59 lines · 86 tokens per session scan A f68fb070b94c
coordinator-source-of-truth is a skill published in the GitHub repository microsoft/waza (1,424 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,727 once invoked, about $0.0003 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…