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 instructions/microsoft/waza/copilot-instructionsgit 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.01232 | $0.01232 |
| Opus 5 | $0.00616 | $0.00616 |
| Sonnet 5 | $0.00246 | $0.00246 |
| Haiku 4.5 | $0.00123 | $0.00123 |
Grade C, and why
waza copilot-instructions.md scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .impeccable web/node_modules site/node_modules How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Coding Agent — Squad Instructions
You are working on a project that uses Squad, an AI team framework. When picking up issues autonomously or using Squad, follow these guidelines.
Coordinator Canary Check
IMPORTANT — run this check only when the session is expected to use Squad Coordinator behavior, before doing any Squad work:
Look for the exact token SQUAD_COORDINATOR_CANARY_a8f3 in your agent_instructions. This token is placed at the end of squad.agent.md. If it is missing, the coordinator file is missing or truncated.
Do not run this check for ordinary Copilot Coding Agent work, or when the user explicitly asks not to use Squad. In that case, proceed without Squad routing, spawning, PR, or branch-protection behavior.
When the token is missing and Squad Coordinator behavior is required, you MUST:
- STOP — do not proceed with standard Squad behavior.
- WARN the user with this exact message:
⚠️ Squad coordinator (squad.agent.md) appears to be missing or truncated. The canary token was not found. Do NOT proceed with standard Squad behavior — Squad's safety rails are not loaded. Please restart your session. - Do not continue with normal Squad routing, spawning, PR, or branch-protection behavior after emitting the warning.
Team Context
Before starting work on any issue:
- Read
.squad/team.mdfor the team roster, member roles, and your capability profile. - Read
.squad/routing.mdfor work routing rules. - If the issue has a
squad:{member}label, read that member's charter at.squad/agents/{member}/charter.mdto understand their domain expertise and coding style — work in their voice.
Capability Self-Check
Before starting work, check your capability profile in .squad/team.md under the Coding Agent → Capabilities section.
- 🟢 Good fit — proceed autonomously.
- 🟡 Needs review — proceed, but note in the PR description that a squad member should review.
- 🔴 Not suitable — do NOT start work. Instead, comment on the issue:
🤖 This issue doesn't match my capability profile (reason: {why}). Suggesting reassignment to a squad member.
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.
- 2d ago First seen · 127 lines · 1,232 tokens per session scan C f3646cef4eaa
waza copilot-instructions.md is an instructions file published in the GitHub repository microsoft/waza (1,288 stars, last pushed 3d ago), licensed MIT. It adds 1,232 tokens to every session, about $0.0062 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.