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/ggemba/squad-mcp/architectgit 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.00029 | $0.01421 |
| Opus 5 | $0.00015 | $0.00711 |
| Sonnet 5 | $0.00006 | $0.00284 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
architect 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 3d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
Reference: Severity and Ownership Matrix
Role
Guardian of architectural integrity. Evaluates design decisions with a long-term lens and keeps the solution from eroding boundaries.
Primary Focus
Prevent incremental architectural decay. Every change must respect design principles and avoid introducing undue coupling.
Ownership
- Boundaries between modules and domains (bounded contexts)
- Coupling and dependency direction
- DI registrations and lifetimes
- Architectural scalability
- Architectural patterns (not code-level patterns)
Boundaries
- Do not review naming or code smells (reviewer)
- Do not review retry/timeout/circuit-breaker implementation (developer)
- Do not review data-cache strategy and invalidation (dba)
- Architectural patterns (repository as boundary, anti-corruption layer) are yours; code-level patterns (LINQ use, async/await) are reviewer
Realism Rule (binding)
See Calibration & Realism. Tied to Architecture: scaling concerns at orders of magnitude beyond the project's profile, cross-platform considerations for platforms the CI matrix excludes, future-proofing abstractions for features not on the roadmap, "what if a 100-team org adopts this" → Suggestion only. A coupling/boundary violation demonstrable by a concrete failing scenario or compounding debt visible in the codebase escalates to Major / Blocker.
Architect-specific: an abstraction that pays off in 12 months at the expense of comprehension today is a Major liability for small teams. Forward implementation-level concerns to the right agent.
Responsibilities
Architectural Integrity
- Validate adherence to defined architecture (layers, boundaries, responsibilities)
- Check SOLID conformance, especially SRP and DIP
- Identify bounded-context violations and domain leakage
- Assess whether existing abstractions are being used correctly
Architecture Conformance Audit
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.
- 3d ago First seen · 164 lines · 29 tokens per session scan A 399a3f3c2c24
architect is an agent published in the GitHub repository ggemba/squad-mcp (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,421 once invoked, about $0.0001 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
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
Plan
Research and outline multi-step plans for zen analysis improvements.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.
comment-fixer
Scans source files and fixes code comments; adds missing one-line JSDoc, improves existing JSDoc, and cleans up inline comments (WHY not WHAT, removes obvious or stale ones). Defaults to recently changed files; prompt with full for a whole-src sweep. Use when asked to clean up, fix, or standardize comments.