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.
git clone --depth 1 https://github.com/ggemba/squad-mcpWrote 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/commands/ggemba/squad-mcp/implement)<a href="https://agentmods.dev/commands/ggemba/squad-mcp/implement"><img src="https://agentmods.dev/badge/commands/ggemba/squad-mcp/implement/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/commands/ggemba/squad-mcp/implement"><img src="https://agentmods.dev/badge/commands/ggemba/squad-mcp/implement.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.00000 | $0.00863 |
| Opus 5.5 | $0.00000 | $0.00345 |
| Sonnet 5.5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
implement 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.
How it starts
The opening of the file, as written. The whole thing — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the squad skill in implement mode for the user's request:
$ARGUMENTS
Execute the skill exactly as specified at skills/squad/SKILL.md. The full contract — Inviolable Rules, phase-by-phase workflow, gates, and edge cases — lives there. This file is a thin trigger; the skill file is the source of truth.
Mode: implement (default). The skill orchestrates the full squad-dev workflow: classify → score risk → select advisory agents → planner → Gate 1 (plan approval) → parallel advisory dispatch → Gate 2 (Blocker halt) → implementation → consolidator → final verdict.
Execution depth (--quick / --deep)
The skill resolves an execution depth from classify+risk signals. Pass mode to compose_squad_workflow per the user's flag, or omit it to let auto-detect choose:
--quick→ cap squad to 2 agents, skiptech-lead-plannerand thetech-lead-consolidatorpersona, reject-loop ceiling at 1 cycle. Aim: sub-30s feedback on small / Low-risk changes. The auto-detect picks this whenrisk == Low && files_count <= 5and no auth/money/migration signals (andwork_type != Security). Example:/squad:implement --quick fix typo in src/utils/format.ts.--normal(the implicit default) → pre-v0.8.0 behaviour: full pipeline, 4–7 agents, 2 reject-loop cycles. Pass--normalexplicitly only to override an auto-detectedquick/deepwhen you want the middle path. Same vocabulary as/brainstorm --normaland/squad:review --normal.--deep→ force-includearchitect+security, allow 3 reject-loop cycles, suggest Codex (still gated on--codexconsent). Auto-detect picks this onrisk == Highorwork_type == Securityor any oftouches_auth / money / migration. Example:/squad:implement --deep refactor src/auth/jwt-validator.
If the user FORCES --quick on a high-risk diff (auth / money / migration), the cap stays at 2 but security is force-included as one of the two. The output will carry mode_warning — surface that to the user, do not bury 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 First seen · 33 lines · 0 tokens per session scan A aa6242883818
implement is a command published in the GitHub repository ggemba/squad-mcp (4 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 863 tokens. 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-08-31.
Other commands, from other repositories
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.
settings
View or update Shipyard workflow settings.
sanity-review
Review code for Sanity best practices and common issues.
develop
Implement skill development issues with TDD-governed workflow.
morning
Review new WhatsApp messages and show the morning summary: only what needs your action today.
favorites
Suggest your favorite contacts from recent conversations and record your decision for each one.