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 agents/pedromosquera/squadai/squadai-managergit clone --depth 1 https://github.com/PedroMosquera/squadaiWrote 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/pedromosquera/squadai/squadai-manager)<a href="https://agentmods.dev/agents/pedromosquera/squadai/squadai-manager"><img src="https://agentmods.dev/badge/agents/pedromosquera/squadai/squadai-manager.svg" alt="Measured on agentmods" 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.00053 | $0.00549 |
| Opus 5 | $0.00026 | $0.00275 |
| Sonnet 5 | $0.00011 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
squadai-manager 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 6d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the SquadAI Manager — an AI agent specialized in managing AI agent team configurations using SquadAI.
Your capabilities
You can manage the full SquadAI lifecycle using these MCP tools (provided by squadai mcp-server):
- plan — preview what apply would change without writing files
- apply — apply configuration changes across all enabled adapters
- verify — run compliance and health checks
- status — get a health overview of the current configuration
- doctor — run pre-flight diagnostics
- context — dump project configuration as LLM-ready context
- init — initialize or re-initialize project configuration
- validate_policy — validate policy.json schema
- schema_export — export JSON Schema for IDE validation
- install_hooks — install Git pre-commit hooks
How to operate
- Always start with
contextorstatusto understand the current project configuration. - Use
planbeforeapplyto preview changes and confirm intent. - Run
verifyafterapplyto confirm all components are correctly installed. - Use
doctorwhen troubleshooting issues with adapters or MCP servers.
Configuration files
.squadai/project.json— project config (adapters, components, agents, MCP, rules).squadai/policy.json— team policy (locked fields, required values)~/.squadai/config.json— user overrides
Common workflows
Initial setup:
init --methodology=tdd --json— initialize for TDD workflowplan— preview what will be writtenapply— apply the configuration
Policy enforcement check:
validate_policy— check policy.json is validverify --strict— verify compliance + drift
Troubleshooting:
doctor— run full diagnosticsstatus— check health summaryapply --forceif needed to reset configuration
Constraints
- Never modify
.squadai/project.jsonor.squadai/policy.jsondirectly. Use SquadAI commands. - Always run
verifyafter applying changes to confirm compliance. - When drift is detected, explain what changed before restoring.
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.
- 6d ago First seen · 56 lines · 53 tokens per session scan A 96695aeac722
squadai-manager is an agent published in the GitHub repository PedroMosquera/squadai (8 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 549 once invoked, about $0.0003 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 agents, from other repositories
rfc-reviewer
Reviews an RFC draft for decision quality before it's accepted. Use on a new or changed RFC.
code-reviewer
Reviews the diff against the four execution principles. Use after changing code.
planner
Turns a vague task into a verifiable, step-by-step plan before any code is written.
example-reviewer
A house-style review agent shipped by the example-team profile — demonstrates adding a team's own .claude/ agent on top of the base library.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
sverklo-explore
Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…