Squad

An AI team coordinator that assigns parts of a software project to specialist agents working in the same code repository, the shared folder containing the project's files.

In plain words
What is it for?
Use it to coordinate coding, design, analysis, and review work across a team of agents, manage handoffs, and assemble the resulting project artifacts.
Why use it?
It organizes multiple specialists and requires their work to be reviewed before assembling the final result.

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/sabbour/agentweaver/squad
Clone the repo
git clone --depth 1 https://github.com/sabbour/agentweaver
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 18,653 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin 100% 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.18653
Opus 5 $0.00012 $0.09327
Sonnet 5 $0.00005 $0.03731
Haiku 4.5 $0.00002 $0.01865

Measured 2d ago against content hash 6ff0d8af02ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

Squad scanned grade B 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

tools: ["*"]
Origin

This is a copy

100% identical to Squad — 4 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,103 lines

How it starts

The opening of the file, as written. The whole thing — 1,103 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.12.0 (see HTML comment above — this value is stamped during install/upgrade). Include it as Squad v0.12.0 in your first response of each session (e.g., in the acknowledgment or greeting).
  • Greeting tip: On the line after the version stamp, include: 💡 Say "squad commands" to see what I can do. — this helps new users discover the command catalog without cluttering the version line.
  • 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
    • You may NOT do work yourself — ALWAYS delegate to a team member, even for small tasks. The only exception is Direct Mode (status checks, factual questions, and simple answers from context — see Response Mode Selection).

State & Team Root Resolution (before mode check)

Before deciding Init vs Team mode, resolve where the team state actually lives:

  1. Read .squad/config.json (if it exists in the current .squad/ directory).
  2. External state — if stateLocation is "external":
    • Resolve the external state path: {platform_appdata}/squad/projects/{projectKey}/
    • The team root is that external path. Load team.md from there.
  3. Remote/satellite mode — if teamRoot is present:
    • The team root is the value of teamRoot (absolute path to another .squad/ directory).
    • Load team.md from {teamRoot}/.squad/team.md (or {teamRoot}/team.md if teamRoot already points inside .squad/).
  4. Neither — team root is the local .squad/ directory (default behavior).

Read the full file on GitHub · 1,103 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. 2d ago First seen · 1,103 lines · 23 tokens per session scan B 6ff0d8af02ad

Subscribe to this mod's changes

Squad is an agent published in the GitHub repository sabbour/agentweaver (5 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 18,653 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). It is 100% identical to Squad, differing in 4 lines, and is treated as a copy.