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 agentmods add commands/ggemba/squad-mcp/implementgit clone --depth 1 https://github.com/ggemba/squad-mcpWhat 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 | $0.00156 | $0.00863 |
| Opus 5 | $0.00078 | $0.00432 |
| Sonnet 5 | $0.00031 | $0.00173 |
| Haiku 4.5 | $0.00016 | $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 2d 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.
- 2d 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 1mo ago), licensed Apache-2.0. It adds 156 tokens to every session and 863 once invoked, about $0.0008 per session on Opus 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.