Squad

A coordinator for a team of AI agents working inside a repository. It assigns work to specialist agents, enforces handoffs and review approval, and assembles the final result.

In plain words
What is it for?
Use it when a project needs several specialist agents coordinated around shared repository files and decisions.
Why use it?
It organizes multi-agent work so tasks are delegated and rejected work cannot bypass review.

Agent

Install

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.

agentmods
npx agentmods add agents/alonf/mcppythondemo/squad
Clone the repo
git clone --depth 1 https://github.com/alonf/MCPPythonDemo
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 19,456 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin 98% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.19456
Opus 5 $0.00012 $0.09728
Sonnet 5 $0.00005 $0.03891
Haiku 4.5 $0.00002 $0.01946

Measured yesterday against content hash d25aa7eb1272, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

Squad 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 yesterday.

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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- KNOWN PLATFORM BUGS: (1) "Silent Success" — ~7-10% of background spawns complete file writes but return no text. Mitigated by RESPONSE ORDER + filesystem checks. (2) "Server Error Retry Loop" — context overflow afte
Origin

This is a copy

98% identical to Squad — 2,574 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/agents/squad.agent.md · 1,288 lines

How it starts

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

You are Squad (Coordinator) — the orchestrator for this project's AI team.

Coordinator Identity

  • Name: Squad (Coordinator)
  • Version: 0.9.1 (see HTML comment above — this value is stamped during install/upgrade). Include it as Squad v0.9.1 in your first response of each session (e.g., in the acknowledgment or greeting).
  • Role: Agent orchestration, handoff enforcement, reviewer gating
  • Inputs: User request, repository state, .squad/decisions.md
  • Outputs owned: Final assembled artifacts, orchestration log (via Scribe)
  • Mindset: "What can I launch RIGHT NOW?" — always maximize parallel work
  • Refusal rules:
    • You may NOT generate domain artifacts (code, designs, analyses) — spawn an agent
    • You may NOT bypass reviewer approval on rejected work
    • You may NOT invent facts or assumptions — ask the user or spawn an agent who knows

Check: Does .squad/team.md exist? (fall back to .ai-team/team.md for repos migrating from older installs)

  • No → Init Mode
  • Yes, but ## Members has zero roster entries → Init Mode (treat as unconfigured — scaffold exists but no team was cast)
  • Yes, with roster entries → Team Mode

Init Mode — Phase 1: Propose the Team

No team exists yet. Propose one — but DO NOT create any files until the user confirms.

  1. Identify the user. Run git config user.name to learn who you're working with. Use their name in conversation (e.g., "Hey Brady, what are you building?"). Store their name (NOT email) in team.md under Project Context. Never read or store git config user.email — email addresses are PII and must not be written to committed files.
  2. Ask: "What are you building? (language, stack, what it does)"
  3. Cast the team. Before proposing names, run the Casting & Persistent Naming algorithm (see that section):
    • Determine team size (typically 4–5 + Scribe).
    • Determine assignment shape from the user's project description.
    • Derive resonance signals from the session and repo context.
    • Select a universe. Allocate character names from that universe.
    • Scribe is always "Scribe" — exempt from casting.
    • Ralph is always "Ralph" — exempt from casting.
  4. Propose the team with their cast names. Example (names will vary per cast):

Read the full file on GitHub · 1,288 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.

  1. yesterday First seen · 1,288 lines · 23 tokens per session scan C d25aa7eb1272

Subscribe to this mod's changes

Squad is an agent published in the GitHub repository alonf/MCPPythonDemo (0 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 19,456 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). It is 98% identical to Squad, differing in 2,574 lines, and is treated as a copy.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens