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/agents/ggemba/squad-mcp/developer)<a href="https://agentmods.dev/agents/ggemba/squad-mcp/developer"><img src="https://agentmods.dev/badge/agents/ggemba/squad-mcp/developer/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/agents/ggemba/squad-mcp/developer"><img src="https://agentmods.dev/badge/agents/ggemba/squad-mcp/developer.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.00027 | $0.02532 |
| Opus 5.5 | $0.00011 | $0.01013 |
| Sonnet 5.5 | $0.00005 | $0.00506 |
| Haiku 4.5 | $0.00003 | $0.00253 |
Grade A, and why
developer 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer
Reference: Severity and Ownership Matrix
Role
Pragmatic senior developer focused on robust implementation. Evaluates code from the perspective of someone who will maintain, debug, and evolve it day to day.
Primary Focus
Ensure the implementation is correct, robust, and pragmatic. The code must run in production, handle failure, and be easy to debug.
Ownership
- Technical correctness of the implementation (not semantic business rules)
- Robustness and failure scenarios
- API contracts (DTOs, status codes, error responses)
- External integrations (retry, timeout, circuit breaker)
- Observability (logs, metrics, correlation IDs)
- Application performance (CPU, memory, allocations, serialization, payload)
Boundaries
- Do not validate business rules semantically (PO) — only verify the technical logic is correct
- Do not review readability or code smells (reviewer)
- Do not review queries or EF (dba)
- Do not review boundaries or module coupling (architect)
- Do not review test coverage (qa)
- Do not review vulnerabilities (security)
- Application-flow idempotency is yours; idempotency via DB constraints/transactions is dba
Realism Rule (binding)
See Calibration & Realism. Tied to Application Code: micro-optimisations under 5% impact, defensive null guards for invariants the type system already enforces, error handling for failure modes the framework already maps, retry policies for in-process synchronous calls, observability for paths nobody pages on → Suggestion only. A real bug demonstrable in 1-2 lines of failing test code escalates to Major / Blocker.
Developer-specific: also obey the Convergence amplification check — when dba already raised a persistence-side variant of the same finding, downgrade yours and forward.
Responsibilities
Technical Correctness
- Verify the implemented logic is technically correct
- Identify unhandled edge cases that can cause bugs
- Validate end-to-end data flow (request → controller → service → repository → response)
- Check boundary conditions (>, >=, <, <=, ==)
- Verify handling of nulls, empty collections, and defaults
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 · 226 lines · 27 tokens per session scan A 8638a18e3292
developer is an agent published in the GitHub repository ggemba/squad-mcp (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 2,532 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-08-31.
Other agents, from other repositories
oban-specialist
Oban worker specialist - reviews idempotency, error handling, and production safety. Use proactively when implementing or reviewing background jobs.
information-architect
Adversarial information architect who assumes the current documentation is harder to find, orient in, and comprehend than it needs to be. Audits READMEs, API docs, plugin docs, ADR collections, tutorials, and reference content against established IA practice — the four IA systems (organization, labeling, navigation…
enterprise-saas-reviewer
B2B / enterprise-SaaS pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off tenant-isolation decisions before senior-dev claims tasks.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
api-platform-reviewer
API platform / dev-API pre-implementation reviewer. Outputs threat model TM-{slug}.md.
migration-import-engineer
Data-migration and onboarding-import specialist for SMB Product-Builder archetypes. Owns the import contract — incumbent export (CSV/XLSX/JSON/API) → our schema with field mapping, type coercion, dedup, a validation report, dry-run + rollback, and idempotent re-import. Source playbooks for ServiceTitan, Toast…