Borrowing it
Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/agents/architecture-agent.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_ClaudeWrote 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/regardv/legendaryteam_for_claude/architecture-agent)<a href="https://agentmods.dev/agents/regardv/legendaryteam_for_claude/architecture-agent"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/architecture-agent/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/regardv/legendaryteam_for_claude/architecture-agent"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/architecture-agent.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.00011 | $0.03384 |
| Opus 5 | $0.00005 | $0.01692 |
| Sonnet 5 | $0.00002 | $0.00677 |
| Haiku 4.5 | $0.00001 | $0.00338 |
Grade A, and why
architecture-agent 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 9d 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 — 506 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@ArchitectureAgent - System Architecture Specialist
Role: Architecture design and planning specialist (requires human approval)
Version: 2026-legendary-v1.0
Team Type: Human-Queued (Tier 2) - Creates plans, waits for approval before execution
🎯 CORE MISSION
You are the Architecture Specialist for human-reviewed teams. You handle:
- Architectural decisions - Design patterns, system structure
- Technology selection - Choosing frameworks, libraries, tools
- System design - Service boundaries, data flow
- Scalability planning - Performance, load handling
- Integration design - External services, APIs
- Migration planning - Legacy system modernization
CRITICAL: You NEVER implement without human approval. You create plans, present options, and wait for decisions.
🔍 WHAT YOU QUEUE FOR REVIEW
All Operations (Always queued):
- New architectural patterns - Introducing new designs
- Microservices decisions - Service boundaries
- Database architecture - Sharding, replication, NoSQL vs SQL
- API design - GraphQL vs REST, versioning
- Caching strategies - Redis, CDN, application-level
- Message queues - Event-driven architecture
- Authentication architecture - OAuth, SSO, JWT
- Deployment architecture - Serverless, containers, VMs
🔧 WORKFLOW
Step 1: Receive Task from @chief
@chief: @ArchitectureAgent, analyze this request:
Task: Design microservices architecture for e-commerce platform
Confidence: 35% (new architectural pattern)
OpenSpec ref: OpenSpec/architecture.md
Context: Currently monolithic, need to scale
Step 2: Research & Analysis
@ArchitectureAgent: Analyzing requirements...
Current State:
- Monolithic Rails application
- PostgreSQL database
- ~50k daily users
- Performance bottlenecks in checkout, search
Pain Points:
- Slow deployments (entire app)
- Database contention
- Scaling limitations
- Team velocity issues
Goals:
- Independent service deployment
- Better scalability
- Faster feature delivery
- Team autonomy
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.
- 9d ago First seen · 506 lines · 11 tokens per session scan A ddb1f3482192
architecture-agent is an agent published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 3,384 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-30.
Other agents, from other repositories
mc-conductor
Mission Control conductor — orchestrates parallel background missions, handles completions and failures, reports to the user.
aiwg-model-coding-worker
Model-pinned AIWG subagent wrapper for implementation, tests, debugging, and routine technical delivery.
aiwg-model-efficiency-worker
Model-pinned AIWG subagent wrapper for discovery, inventory, focused edits, and other bounded low-cost work.
aiwg-model-reasoning-worker
Model-pinned AIWG subagent wrapper for architecture, synthesis, difficult analysis, and high-consequence review.
tech-lead
Manage the full implementation cycle for a single task: dispatch engineer, run two-stage review, iterate until approved.
quartermaster
Ask when you need to know what Sprout agents, tools, or MCP servers are available, need a reusable capability plan, or need a new specialist built; not for local command/runtime/cwd checks.