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/paulyuk/snap-squad/copilot-instructionsgit clone --depth 1 https://github.com/paulyuk/snap-squadWrote 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/instructions/paulyuk/snap-squad/copilot-instructions)<a href="https://agentmods.dev/instructions/paulyuk/snap-squad/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/paulyuk/snap-squad/copilot-instructions.svg" alt="Measured on agentmods" 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 | $0.00484 | $0.00484 |
| Opus 5 | $0.00242 | $0.00242 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
snap-squad copilot-instructions.md 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 4d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — The Default Squad
You are part of a squad. This repository uses multi-agent team coordination.
On Every Session
- Read
AGENTS.mdat repo root for universal squad instructions - Read
CLAUDE.mdat repo root for session memory and project context - Read
.squad/team.mdfor the full team roster - Read
.squad/routing.mdfor work routing rules - Check
.squad/decisions.mdbefore starting work
Squad-Aware Behavior
- Identify which squad member is best suited for the current task
- Start every substantive response with a role tag:
> **[AgentName]**(see AGENTS.md for format rules) - Adopt their expertise, voice, and boundaries
- Dispatch squad members as parallel sub-agents using the
tasktool withmode: "background". Include charter context from.squad/agents/<name>/charter.md. See AGENTS.md "Squad Dispatch" section. - Log significant decisions to
.squad/decisions.mdafter completing work
Proactive Quality Triggers
These fire automatically — they are not optional:
| Trigger | Action |
|---|---|
| Code changed | Run npm test before committing — never commit red |
| User-visible behavior changed | Update docs and README if affected |
| Prompt or agent behavior changed | Review eval baselines |
| Important trade-off made | Log decision to .squad/decisions.md |
| Meaningful milestone reached | Update JOURNAL.md with what happened and why |
| Another role's expertise needed | Dispatch that role as a background sub-agent via task tool |
Before You Respond With "Done"
Verify that all triggered duties above were handled or explicitly called out as deferred. Do not silently skip them.
Managing This Squad
This squad was created with snap-squad. If the user asks to change, reset, or switch their squad:
npx snap-squad init --type <preset> --force # switch to a different preset
npx snap-squad list # see available presets
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.
- 4d ago First seen · 49 lines · 484 tokens per session scan A 011151747ee1
snap-squad copilot-instructions.md is an instructions file published in the GitHub repository paulyuk/snap-squad (19 stars, last pushed 5mo ago), licensed MIT. It adds 484 tokens to every session, about $0.0024 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 instructions, from other repositories
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).
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.
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.