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.
Borrowing it
Nothing to install: this file belongs to bradygaster/squad. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bradygaster/squad/dev/.copilot/skills/content-scope/SKILL.mdgit 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/content-scope)<a href="https://agentmods.dev/skills/bradygaster/squad/content-scope"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/content-scope/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/content-scope"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/content-scope.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.00015 | $0.00249 |
| Opus 5.5 | $0.00006 | $0.00100 |
| Sonnet 5.5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
content-scope 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.
What it actually says
Context
Use this skill when deciding whether proposed documentation, examples, or external material belongs in Squad documentation.
Patterns
- Apply the “Squad ships it” test: keep behavior, configuration, and integration contracts that Squad ships; exclude external infrastructure that users build around Squad.
- When documenting a platform feature used with Squad, identify it as a platform integration rather than implying Squad implements the platform feature.
- Preserve reusable product guidance while linking to external examples, articles, or deployment material instead of importing their operational specifics into product documentation.
Examples
An explanation of Squad’s configured GitHub integration belongs in the documentation. A bespoke bot, webhook deployment, or private operations wrapper built around it belongs in its own project or external reference.
Anti-Patterns
- Calling external infrastructure a built-in Squad feature
- Deleting all integration documentation because the platform owns the underlying service
- Copying third-party operational playbooks into product docs without a shipped contract
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 · 34 lines · 15 tokens per session scan A 993b4767e4b9
content-scope is a skill published in the GitHub repository bradygaster/squad (3,295 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 249 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-12.
Other skills, from other repositories
Codex
Mission control: create tasks, assign to an agent/team, wait for human approval, worker runs in the background, accept results.
squads-cli
Squads CLI — operate your squads through the loop; intent in, reviewed work out. TRIGGER when running squads, dispatching agents, triaging the inbox, reading/writing memory, recording feedback, or checking status/usage.
ponytail-debt
Harvest every ponytail: comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or…
gh
You have access to gh (GitHub CLI) for repository and project management.
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…
apex-workflow-start
Start or resume APEX work in VS Code Copilot. Select the interactive Orchestrator or domain owner, recover current project evidence, collect missing decisions and use native tasks without UI handoff or readiness rituals.