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 agentmods add skills/bradygaster/squad/squad-commandsnpx skills add bradygaster/squad --skill squad-commandsgit 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/squad-commands)<a href="https://agentmods.dev/skills/bradygaster/squad/squad-commands"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/squad-commands.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.02652 |
| Opus 5 | $0.00017 | $0.01326 |
| Sonnet 5 | $0.00007 | $0.00530 |
| Haiku 4.5 | $0.00003 | $0.00265 |
Grade A, and why
squad-commands 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 5d 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
97% identical to squad-commands — 6 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Menu Presentation Rules
When the user triggers this skill ("squad commands", "help", "what can squad do", etc.):
- Category-level menu first. Present category names as an
ask_userchoice list:📋 Squad Commands — pick a category: 1. Install & Upgrade 2. Team Management 3. Issues & PRs 4. Plugins & Skills 5. Model & Cost 6. Sessions & State - Drill-down. After selection, show operation titles in that category as a second
ask_userlist. - Direct match skips the menu. If the user says "how do I upgrade with state backend," match to the specific entry and go straight to argument collection.
- Compact fallback. If
ask_useris unavailable, render as a markdown table instead. - Back / Cancel. Include "← Back to categories" in sub-menus. Include "Cancel" in confirmation prompts. Respect "never mind" / "cancel" at any point.
Argument collection: For entries with args, iterate the list sequentially. Use ask_user with choices when choices is provided; free-text prompt otherwise. If the user says "just do it" or "defaults are fine," skip remaining args and use their defaults.
Confirmation template:
⚠️ This will {action-description}.
{what will change}
Proceed? (yes / no)
Install & Upgrade
Upgrade Squad CLI
- intent: upgrade squad, update squad, install latest version, get new version
- summary: Upgrade Squad CLI to the latest version for your channel
- action: shell
- command: squad upgrade
- args:
state-backend: Which state backend? | choices: {worktree, git-notes, orphan, two-layer} | default: (keep current)
- confirm: false
- platform_caveats: Requires terminal. In VS Code, open the integrated terminal and run the command directly.
Initialize Squad
- intent: set up squad, initialize squad, create team, start squad in this project
- summary: Scaffold Squad in the current directory (idempotent)
- action: shell
- command: squad init
- args: (none)
- confirm: false
- platform_caveats: Requires terminal. Recommend a standalone terminal for best results.
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.
- 5d ago First seen · 304 lines · 34 tokens per session scan A 961127c20d85
squad-commands is a skill published in the GitHub repository bradygaster/squad (3,154 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 2,652 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to squad-commands, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
mutation-testing
Use when running mutation testing, killing mutants, verifying test quality, checking mutation score, or analyzing survivors after the test baseline is green.
generate-microcks-openapi-samples
Use when creating OpenAPI mock examples for Microcks, setting up request/response routing with dispatchers, or mapping request fields to mock responses.
extracting-code-structure
Use when listing all methods, functions, or classes in a file, exploring unfamiliar code, getting API overviews, or deciding what to read selectively without loading entire files.
setup-husky-dotnet
Use when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically.
azure-bicep-patterns
UTILITY SKILL — Reusable Azure Bicep patterns: hub-spoke, private endpoints, diagnostics, AVM composition. WHEN: "hub-spoke Bicep", "private endpoint module", "diagnostic settings", "AVM Bicep composition". USE FOR: Bicep template design, hub-spoke networking, private endpoint patterns, AVM modules. DO NOT USE FOR…