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 personal-squadgit 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/personal-squad)<a href="https://agentmods.dev/skills/bradygaster/squad/personal-squad"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/personal-squad/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/personal-squad"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/personal-squad.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.00014 | $0.00515 |
| Opus 5.5 | $0.00006 | $0.00206 |
| Sonnet 5.5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
personal-squad 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 personal-squad — 0 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Personal Squad — Skill Document
What is a Personal Squad?
A personal squad is a user-level collection of AI agents that travel with you across projects. Unlike project agents (defined in a project's .squad/ directory), personal agents live in your global config directory and are automatically discovered when you start a squad session.
Directory Structure
~/Library/Application Support/squad/personal-squad/ # macOS
~/.config/squad/personal-squad/ # Linux
%APPDATA%/squad/personal-squad/ # Windows
├── agents/
│ ├── {agent-name}/
│ │ ├── charter.md
│ │ └── history.md
│ └── ...
└── config.json # Optional: personal squad config
How It Works
- Ambient Discovery: When Squad starts a session, it checks for a personal squad directory
- Merge: Personal agents are merged into the session cast alongside project agents
- Ghost Protocol: Personal agents can read project state but not write to it
- Kill Switch: Set
SQUAD_NO_PERSONAL=1to disable ambient discovery
Commands
squad personal init— Bootstrap a personal squad directorysquad personal list— List your personal agentssquad personal add {name} --role {role}— Add a personal agentsquad personal remove {name}— Remove a personal agentsquad cast— Show the current session cast (project + personal)
Ghost Protocol
See templates/ghost-protocol.md for the full rules. Key points:
- Personal agents advise; project agents execute
- No writes to project
.squad/state - Transparent origin tagging in logs
- Project agents take precedence on conflicts
Configuration
Optional config.json in the personal squad directory:
{
"defaultModel": "auto",
"ghostProtocol": true,
"agents": {}
}
Environment Variables
SQUAD_NO_PERSONAL— Set to any value to disable personal squad discoverySQUAD_PERSONAL_DIR— Override the default personal squad directory path
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 First seen · 67 lines · 14 tokens per session scan A 991d18493e4d
personal-squad is a skill published in the GitHub repository bradygaster/squad (3,300 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 515 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to personal-squad, differing in 0 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.