What is snap-squad CLAUDE.md?

Session instructions for a repository that uses a team of cooperating coding agents. They define the project context, the session-start reading order, team routing, memory updates, and when to send work to another agent.

Use them at the start of work in the Snap Squad repository, especially when coordinating team members, checking project records, or deciding what tests and documentation are needed.

They give agents shared context and a consistent way to decide who handles a task. This helps preserve decisions and project knowledge between sessions.

How paulyuk/snap-squad configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to paulyuk/snap-squad. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/paulyuk/snap-squad/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/paulyuk/snap-squad

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/paulyuk/snap-squad/claude-md/github.svg)](https://agentmods.dev/instructions/paulyuk/snap-squad/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/paulyuk/snap-squad/claude-md"><img src="https://agentmods.dev/badge/instructions/paulyuk/snap-squad/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/paulyuk/snap-squad/claude-md"><img src="https://agentmods.dev/badge/instructions/paulyuk/snap-squad/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 561 This file is loaded in full into every session.

When invoked 561 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00561	$0.00561
Opus 5.5	$0.00224	$0.00224
Sonnet 5.5	$0.00112	$0.00112
Haiku 4.5	$0.00056	$0.00056

Measured 2mo ago against content hash 17b59e9ef4b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

snap-squad CLAUDE.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 2mo 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.

CLAUDE.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md — The Default Squad Session Memory

Read this at the start of every session. Update when context changes.

Identity

You are working in a repository using the The Default Squad squad preset.

You are part of a squad. Read .squad/team.md for the full roster.

Project Context

Owner: unknown
Squad: The Default Squad (friendly)
Theme: Community Builders

Session Start Protocol

Immediately after reading this file, before responding to the user:

Read .squad/team.md, .squad/routing.md, and .squad/decisions.md
Determine which squad member should lead this task
Begin your first response with the role tag: > **[AgentName]** — this proves squad routing is active
Check whether JOURNAL.md has recent entries — if stale, plan to update it
Identify downstream needs: will this work require tests? docs? evals? decisions? Include them in your plan.
Dispatch, don't role-play. Use the task tool to launch squad members as background sub-agents with their charter context. See AGENTS.md "Squad Dispatch" section.

Non-Optional Operating Behaviors

These apply in every session, whether or not the user asks:

Code changed → run npm test before committing. Never commit without a green test run. If tests fail, fix them or explain why.
Behavior changed → docs updated. If what the user sees changed, docs must change too.
Trade-off made → decision logged. Record it in .squad/decisions.md with context and reasoning.
Milestone reached → journal updated. JOURNAL.md captures the story, not just the code.
Another role's domain touched → dispatch that role as a sub-agent. Don't role-switch — use the task tool.

Session Completion Gate

Before ending the session, verify:

.squad/decisions.md — Updated if any decisions were made
JOURNAL.md — Updated if a milestone was reached
Relevant docs — Updated if user-visible behavior changed
Open risks or follow-ups — Explicitly called out, not silently dropped

Read the full file on GitHub · 54 lines

Changes

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.

2mo ago First seen · 54 lines · 561 tokens per session scan A 17b59e9ef4b8

Subscribe to this mod's changes

snap-squad CLAUDE.md is an instructions file published in the GitHub repository paulyuk/snap-squad (19 stars, last pushed 7mo ago), licensed MIT. It adds 561 tokens to every session, about $0.0022 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-08-30.

Building agents Memory and context

snap-squad CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
snap-squad CLAUDE.mdpaulyuk/snap-squad	Instructions file	19	7mo ago	MIT	A	561	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

snap-squad: Instructions file for Claude Code