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 squad-version-checkgit 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-version-check)<a href="https://agentmods.dev/skills/bradygaster/squad/squad-version-check"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/squad-version-check/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/squad-version-check"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/squad-version-check.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.00052 | $0.01702 |
| Opus 5.5 | $0.00021 | $0.00681 |
| Sonnet 5.5 | $0.00010 | $0.00340 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
squad-version-check 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 squad-version-check — 4 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Squad CLI Internals — Version Stamping & Upgrade Mechanics
Confidence: medium Discovered by: repository investigation Date: 2026-05-26 Validated in: Issue #1173 recon (bradygaster/squad)
What This Skill Covers
Reusable knowledge about how @bradygaster/squad-cli stamps its version into squad.agent.md, how squad upgrade works, what it preserves vs. overwrites, and how to probe the npm registry for the latest version from a coordinator prompt.
Package & Registry Facts
- Package name:
@bradygaster/squad-cli - Registry: npm (public)
- CLI binary:
squad(registered viapackage.json#bin.squad) - Node version requirement: Node ≥22.5.0 (ESM-only codebase)
Version Stamping Mechanism
Source file: dist/cli/core/version.js
Three functions:
getPackageVersion()
Walks up from the compiled JS file to find package.json. Returns pkg.version. Works from both dist/cli/core/version.js and a bundled root cli.js. Returns '0.0.0' as fallback if not found.
stampVersion(filePath, version)
Mutates squad.agent.md in three places:
- HTML comment:
<!-- version: {version} -->(must be on the line immediately after frontmatter---) - Identity line:
- **Version:** {version} - Greeting instruction: backtick-quoted
`Squad v{version}`
Called by: both init and upgrade — after copying the template to the destination.
readInstalledVersion(filePath)
Reads the stamped version back from squad.agent.md:
- First tries HTML comment format:
/<!-- version: ([0-9.]+(?:-[a-z]+(?:\.\d+)?)?) -->/ - Falls back to old frontmatter format:
/^version:\s*"([^"]+)"/m - Returns
'0.0.0'on any error
squad upgrade Behavior
Source file: dist/cli/core/upgrade.js
What gets overwritten:
squad.agent.md— full overwrite from template, thenstampVersion()- Files with
overwriteOnUpgrade: trueinTEMPLATE_MANIFEST: casting JSON files, template .md files,copilot-instructions.md(if @copilot enabled) - GitHub Actions workflows — from
templates/workflows/; non-npm projects get type-aware stubs - Runs
runMigrations()after file copy
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 f75495722a6b
- 1mo ago First seen · 170 lines · 52 tokens per session scan A c533dd40c207
squad-version-check is a skill published in the GitHub repository bradygaster/squad (3,300 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,702 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to squad-version-check, differing in 4 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.