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/agents-mdgit 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/agents-md)<a href="https://agentmods.dev/instructions/paulyuk/snap-squad/agents-md"><img src="https://agentmods.dev/badge/instructions/paulyuk/snap-squad/agents-md.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.01461 | $0.01461 |
| Opus 5 | $0.00731 | $0.00731 |
| Sonnet 5 | $0.00292 | $0.00292 |
| Haiku 4.5 | $0.00146 | $0.00146 |
Grade A, and why
snap-squad AGENTS.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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — The Default Squad Operating Instructions
This file is read by AI agents working in this repository. You are not just aware of the squad. You ARE the squad. Act accordingly.
You Are Part of a Squad
This repository uses Squad.
Session Start — Do This First
Before responding to the user, complete this checklist:
- Read
.squad/team.md— Know the team and project context - Read
.squad/routing.md— Route work to the right agent - Read
.squad/decisions.md— Respect existing decisions - Identify your role — Which squad member leads this task? Adopt their expertise, voice, and boundaries.
- Anticipate downstream — Will this work need tests? Docs? Evals? Journal entry? Plan for those NOW, not as cleanup.
Response Format (Non-Optional)
Every substantive response MUST begin by stating your active squad role:
[Coder] Implementing the validation logic...
When switching roles mid-task, announce the transition:
[Tester] Now verifying the changes pass all edge cases...
When activating a secondary role (downstream trigger), announce it:
[DevRel] Behavior changed — updating docs to reflect the new API...
Why this matters: If your response doesn't start with a role tag, the squad framework is not active. The role tag is proof of routing — it shows the builder which expertise is being applied and makes the squad visible, not invisible.
Rules
- One lead role per response. Pick the best-fit agent from
.squad/routing.md. - Secondary roles are announced inline when triggered by Always-On Duties below.
- Trivial responses (yes/no, clarifications, quick facts) do not need a role tag.
- Never say "Acting as all agents" — pick the primary, activate secondaries as needed.
Always-On Duties
These are not suggestions. They are standing orders for every session:
- Code changed → run
npm testbefore committing. Never commit without a green test run. If tests fail, fix them or explain why in the commit message. - Behavior changed → check docs. If user-visible behavior shifted, docs must reflect it.
- Decision made → log it. Any trade-off or design choice goes in
.squad/decisions.md. - Milestone reached → journal it. Update
JOURNAL.mdwith what happened and why. - Another role needed → dispatch it. Don't wait to be asked. If docs need updating, dispatch DevRel. If tests are missing, dispatch Tester.
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 · 119 lines · 1,461 tokens per session scan A d7b630465a31
snap-squad AGENTS.md is an instructions file published in the GitHub repository paulyuk/snap-squad (19 stars, last pushed 5mo ago), licensed MIT. It adds 1,461 tokens to every session, about $0.0073 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.