bradygaster/squad is a tool that creates a human-directed team of AI development agents inside a project repository through GitHub Copilot. Developers use it to delegate work among persistent specialists such as frontend, backend, testing, and lead agents while retaining responsibility for decisions and review. The catalogue entries are the skills, agents, and instructions that define and coordinate those team members.
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 skills add bradygaster/squad --skill coordinator-response-modegit clone --depth 1 https://github.com/bradygaster/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/skills/bradygaster/squad/coordinator-response-mode)<a href="https://agentmods.dev/skills/bradygaster/squad/coordinator-response-mode"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/coordinator-response-mode/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.
<a href="https://agentmods.dev/skills/bradygaster/squad/coordinator-response-mode"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/coordinator-response-mode.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00079 | $0.01171 |
| Opus 5.5 | $0.00032 | $0.00468 |
| Sonnet 5.5 | $0.00016 | $0.00234 |
| Haiku 4.5 | $0.00008 | $0.00117 |
Grade A, and why
coordinator-response-mode 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 1mo 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.
This is a copy
100% identical to coordinator-response-mode — 2 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load this skill when: you have routed work to an agent and need to pick the response mode (Direct / Lightweight / Standard / Full). The 1-line stub in
squad.agent.mdis for awareness; this skill is the full decision table + templates.
Response Mode Selection
After routing determines WHO handles work, select the response MODE based on task complexity. Bias toward upgrading — when uncertain, go one tier higher rather than risk under-serving.
| Mode | When | How | Target |
|---|---|---|---|
| Direct | Status checks, factual questions the coordinator already knows, simple answers from context | Coordinator answers directly — NO agent spawn | ~2-3s |
| Lightweight | Single-file edits, small fixes, follow-ups, simple scoped read-only queries | Spawn ONE agent with minimal prompt (see Lightweight Spawn Template below). Use agent_type: "explore" for read-only queries |
~8-12s |
| Standard | Normal tasks, single-agent work requiring full context | Spawn one agent with full ceremony — charter inline, history read, decisions read. This is the current default | ~25-35s |
| Full | Multi-agent work, complex tasks touching 3+ concerns, "Team" requests | Parallel fan-out, full ceremony, Scribe included | ~40-60s |
Direct Mode exemplars
Coordinator answers instantly, no spawn:
- "Where are we?" → Summarize current state from context: branch, recent work, what the team's been doing. A user favorite — make it instant.
- "How many tests do we have?" → Run a quick command, answer directly.
- "What branch are we on?" →
git branch --show-current, answer directly. - "Who's on the team?" → Answer from
team.mdalready in context. - "What did we decide about X?" → Answer from
decisions.mdalready in context.
Lightweight Mode exemplars
One agent, minimal prompt:
- "Fix the typo in README" → Spawn one agent, no charter, no history read.
- "Add a comment to line 42" → Small scoped edit, minimal context needed.
- "What does this function do?" →
agent_type: "explore"(Haiku model, fast). - Follow-up edits after a Standard/Full response — context is fresh, skip ceremony.
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.
- 1mo ago Changed 162c8e52d59b
- 1mo ago First seen · 98 lines · 79 tokens per session scan A 9e022fe051a6
coordinator-response-mode is a skill published in the GitHub repository bradygaster/squad (3,300 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 1,171 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to coordinator-response-mode, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
Video Downloader (yt-dlp)
Download videos from YouTube, TikTok, and 50+ platforms.
ponytail-gain
Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".
omk-mcp-setup
Inspect Neo bundled skills and curated stdio MCP presets, explain permissions and network effects, and configure only explicitly selected servers without overwriting existing user configuration or claiming untested connectivity.
clean-architecture-dotnet
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
outside-in-tdd
Use when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge.
searching-text
Use when searching for text patterns across files, finding specific code locations, or getting lines with surrounding context in a single call.