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/reskill/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/reskill)<a href="https://agentmods.dev/skills/bradygaster/squad/reskill"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/reskill/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/reskill"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/reskill.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.01223 |
| Opus 5.5 | $0.00006 | $0.00489 |
| Sonnet 5.5 | $0.00003 | $0.00245 |
| Haiku 4.5 | $0.00001 | $0.00122 |
Grade A, and why
reskill 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
95% identical to reskill — 69 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
When the coordinator hears "team, reskill" (or similar: "optimize context", "slim down charters"), trigger a team-wide optimization pass. The goal: reduce per-agent context consumption by extracting shared patterns from charters and histories into reusable skills.
This is a periodic maintenance activity. Run whenever charter/history bloat is suspected or a team will be re-cast. Charters and histories are evidence, not the authority for current product behavior: reconcile candidates against current source, workflows, tests, documentation, skills, and decisions before preserving them.
Process
Step 1: Audit
Read all active agent charters and histories, then inventory existing skills. Measure byte sizes. Identify:
- Boilerplate — sections repeated across ≥3 charters with <10% variation (collaboration, model, boundaries template)
- Shared knowledge — domain knowledge duplicated in 2+ charters (incident postmortems, technical patterns)
- Mature learnings — recurring history lessons that should be promoted to skills
- Retirement-critical knowledge — any still-current reusable procedure, constraint, incident lesson, or repository operating fact that would be lost if a charter or history were deleted
Step 2: Extract
For each reconciled pattern:
- Create or update the skill in the location that matches its activation surface:
.squad-templates/skills/{skill-name}/SKILL.mdfor reusable skills shipped in generated Squad templates,.github/skills/{skill-name}/SKILL.mdfor repository-local or GitHub Agentic Workflow procedures, or.squad/skills/{skill-name}/SKILL.mdfor Squad-specific coordinator procedures. Do not treat.copilot/skills/as a destination for new skills; it is the legacy install path. - Follow the skill template format (frontmatter + Context + Patterns + Examples + Anti-Patterns)
- Keep the location consistent with the procedure's real entry point instead of copying the same contract into multiple trees without intent
- Set confidence from the evidence, not the number of charters that contained it
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 · +35 lines · +2 tokens per session 7bad1e5df94b
- 1mo ago First seen · 93 lines · 12 tokens per session scan A 660f1992963a
reskill is a skill published in the GitHub repository bradygaster/squad (3,295 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 1,223 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to reskill, differing in 69 lines, and is treated as a copy.
Other skills, from other repositories
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".
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).
Video Downloader (yt-dlp)
Download videos from YouTube, TikTok, and 50+ platforms.
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.
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.