Squad

An AI team coordinator that organizes specialist agents working in a repository. It manages their handoffs, review approvals, and final assembled work.

In plain words
What is it for?
Use it to set up or run a repository-based AI team. It can initialize a team when no roster exists and coordinate work when a team is already configured.
Why use it?
It gives a project a defined process for dividing work among agents and checking their results. It also prevents the coordinator from inventing facts or producing specialist work without the appropriate agent.

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/webmaxru/is-ai-native/squad
Clone the repo
git clone --depth 1 https://github.com/webmaxru/is-ai-native
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,328 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.19328
Opus 5 $0.00012 $0.09664
Sonnet 5 $0.00005 $0.03866
Haiku 4.5 $0.00002 $0.01933

Measured 2d ago against content hash dfd8bcc35902, 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 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.

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 — 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,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. 2d ago First seen · 1,288 lines · 23 tokens per session scan C dfd8bcc35902

Subscribe to this mod's changes

Squad is an agent published in the GitHub repository webmaxru/is-ai-native (5 stars, last pushed 10d ago), licensed MIT. It adds 23 tokens to every session and 19,328 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 4 lines, and is treated as a copy.

Related

Other agents, from other repositories

challenger

I handle: Fact-checking, counter-hypothesis testing, verification, constructive challenge I do not handle: Implementation, code writing, architecture design — I review, not build On rejection: Specific items needing correction + verification methods provided.

bradygaster/squad · 0 tokens

Update Copilot CompletionAlgorithm

Synchronize this repository's Copilot completion behavior with a pinned microsoft/vscode commit while preserving reviewed completion effects and provenance.

smallmain/vscode-unify-chat-provider · 30 tokens

Update Cli Clients

Regularly maintain certain clients.

smallmain/vscode-unify-chat-provider · 10 tokens

01-Orchestrator

Master orchestrator for the multi-step Azure platform engineering workflow. Coordinates Requirements, Architect, Design, IaC Plan, IaC Code, Deploy agents with mandatory human approval gates. Routes Bicep or Terraform tracks via decisions.iactool.

jonathan-vella/apex-accelerator · 53 tokens

04g-Governance

Azure governance discovery agent. Queries Azure Policy assignments via REST API (incl. management-group-inherited policies), classifies effects, produces governance constraint artifacts, and runs adversarial review. Step 3.5: after Architecture, before IaC Planning.

jonathan-vella/apex-accelerator · 56 tokens

05-IaC Planner

Expert Azure IaC planner that creates comprehensive machine-readable implementation plans. Consults Microsoft documentation, evaluates Azure Verified Modules (Bicep or Terraform), designs full infrastructure solutions with architecture diagrams. Routes by decisions.iactool.

jonathan-vella/apex-accelerator · 50 tokens