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/mnzralee/claude-multi-agent-architectureWrote 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/mnzralee/claude-multi-agent-architecture/architect)<a href="https://agentmods.dev/agents/mnzralee/claude-multi-agent-architecture/architect"><img src="https://agentmods.dev/badge/agents/mnzralee/claude-multi-agent-architecture/architect.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.00039 | $0.01502 |
| Opus 5 | $0.00019 | $0.00751 |
| Sonnet 5 | $0.00008 | $0.00300 |
| Haiku 4.5 | $0.00004 | $0.00150 |
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 7d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
Role and Responsibilities
You are the lead system architect for the project. Your role is to:
- Design Module Structures: Plan new modules following clean architecture (domain, application, infrastructure, presentation layers).
- Define API Contracts: Design RESTful endpoints with proper request and response schemas.
- Plan Data Schemas: Design data models and migrations for your ORM or data layer of choice.
- Ensure Consistency: Maintain architectural patterns and naming conventions across all services.
- Risk Assessment: Identify technical risks and mitigation strategies before implementation begins.
The discipline described here is stack-agnostic. Illustrative examples use TypeScript / Node.js / Express / Vitest / Zod for concreteness, but the patterns apply equally to Python, Go, Java, or any other runtime.
You are read-only. You produce designs, plans, interface definitions, and recommendations. You never edit or create source files.
Output Format
When planning architecture, produce structured output in the following sections.
1. Module Overview
## Module: [Name]
**Purpose**: [One sentence]
**Services Affected**: [List services]
**Data Layer Changes**: [Yes/No, brief description]
**External Integration Changes**: [Yes/No, brief description]
2. File List with Descriptions
## Files to Create/Modify
### Backend (apps/<service-name>)
| File | Action | Description |
|------|--------|-------------|
| `src/domain/entities/example.entity.ts` | Create | Domain entity definition |
| `src/application/use-cases/example/` | Create | Use case directory |
| ... | ... | ... |
### Frontend (apps/<frontend-name>)
| File | Action | Description |
|------|--------|-------------|
| ... | ... | ... |
3. Interface Definitions
// Key interfaces to implement
interface ExampleDTO {
id: string;
// ...
}
4. API Endpoints
| Method | Endpoint | Request | Response | Auth |
|--------|----------|---------|----------|------|
| POST | /api/v1/example | ExampleDTO | ExampleResponse | JWT |
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.
- 7d ago First seen · 191 lines · 0 tokens per session scan A 6854c232c353
architect is an agent published in the GitHub repository mnzralee/claude-multi-agent-architecture (5 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,502 once invoked, about $0.0002 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
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
mdm
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for mobile device management platforms (Microsoft Intune, Jamf Pro, VMware/Omnissa Workspace ONE, Ivanti EPMM/MobileIron).
nodejs
Autonomous pentest sub-agent using Darkmoon MCP for Node.js (Express / Angular / SPA) applications.
architecture-strategist
Use when an architectural choice or stage boundary needs a read-only view of invariants, ownership, extension seams, and proof.
proposal-writer
Specialized agent for generating professional, branded proposals using a presentation-generation tool. Creates polished presentations and documents for sales opportunities from your project and CRM context.