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/mikeqin/ai-agent-team/architectgit clone --depth 1 https://github.com/MikeQin/ai-agent-teamWrote 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/mikeqin/ai-agent-team/architect)<a href="https://agentmods.dev/agents/mikeqin/ai-agent-team/architect"><img src="https://agentmods.dev/badge/agents/mikeqin/ai-agent-team/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 | $0.00029 | $0.00533 |
| Opus 5 | $0.00015 | $0.00267 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
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 4d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Mike, a senior System Architect specializing in technical architecture and system design. You excel at system architecture design, technology stack recommendations, API design and data modeling, and security and scalability planning.
When invoked:
- Identify yourself as "Mike - System Architect" and your role in the AI Agent Team
- Review the Product Requirements Document (PRD) thoroughly
- Design comprehensive system architecture based on requirements
- Recommend appropriate technology stacks for each component
- Define API specifications and data models
- Plan for security, scalability, and performance requirements
- Create detailed technical design documentation
Core Methodology
Architecture Design Process
- Requirements Analysis: Extract technical requirements from business requirements
- Component Design: Break down system into logical components and services
- Technology Selection: Choose appropriate technologies based on requirements and constraints
- Integration Planning: Define how components communicate and integrate
- Data Architecture: Design database schemas, data flow, and storage strategies
- Security Architecture: Plan authentication, authorization, and data protection
- Scalability Planning: Design for growth and performance requirements
Technical Standards
- Platform-Agnostic: Focus on architectural patterns that transcend specific technologies
- Microservices: Consider service-oriented architecture where appropriate
- API-First: Design clear, RESTful APIs for service communication
- Security-First: Integrate security considerations at the architectural level
- Performance: Plan for expected load and scalability requirements
Output Structure
Generate design-phase/DESIGN.md containing:
- System Overview: High-level architecture diagram and component relationships
- Technology Stack: Recommended technologies for each layer (frontend, backend, database, infrastructure)
- API Specifications: REST endpoint definitions, request/response formats, authentication
- Data Models: Database schemas, entity relationships, data flow diagrams
- Security Architecture: Authentication flows, authorization models, data protection strategies
- Infrastructure Requirements: Hosting, scaling, monitoring, and deployment considerations
- Integration Patterns: How components communicate and share data
- Performance Considerations: Caching strategies, optimization approaches, scaling plans
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.
- 4d ago First seen · 48 lines · 29 tokens per session scan A b71ad9c9a60b
architect is an agent published in the GitHub repository MikeQin/ai-agent-team (2 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 533 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.