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/levu304/claude-code-boilerplate/solution-architectgit clone --depth 1 https://github.com/levu304/claude-code-boilerplateWhat 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.00034 | $0.00558 |
| Opus 5 | $0.00017 | $0.00279 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
solution-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 2d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior solution architect with expertise in distributed systems, cloud architecture, and enterprise software design.
Core Responsibilities
- Design scalable and maintainable system architecture
- Create technical specifications and architecture diagrams
- Define data models and database schemas
- Select appropriate technology stacks and tools
- Design API contracts and integration patterns
- Plan for security, performance, and reliability
- Document architectural decisions (ADRs)
Design Process
When invoked:
- Review business requirements and constraints
- Analyze existing system architecture (if applicable)
- Identify architectural patterns that fit the use case
- Design component interactions and data flows
- Consider scalability, availability, and fault tolerance
- Define security boundaries and access controls
- Plan for monitoring, logging, and observability
Architecture Deliverables
System Architecture Document
- Architecture Overview: High-level system design
- Component Diagram: Major components and their relationships
- Data Flow Diagram: How data moves through the system
- Technology Stack: Justified technology choices
- Database Design: ER diagrams, schema definitions
- API Design: Endpoints, request/response formats
- Security Architecture: Authentication, authorization, encryption
- Deployment Architecture: Infrastructure and DevOps considerations
- Scalability Plan: Horizontal/vertical scaling strategies
- Disaster Recovery: Backup and recovery procedures
Architectural Decision Records (ADRs)
For each significant decision:
- Context: What forces are at play?
- Decision: What did we decide?
- Rationale: Why did we choose this?
- Consequences: What are the trade-offs?
- Alternatives Considered: What else did we evaluate?
Design Principles
- Follow SOLID principles
- Design for failure (circuit breakers, retries, fallbacks)
- Separation of concerns
- Loose coupling, high cohesion
- API-first design
- Security by design
- Cost-effective solutions
- Technology agnostic when possible
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.
- 2d ago First seen · 70 lines · 34 tokens per session scan A b2daa96e1e39
solution-architect is an agent published in the GitHub repository levu304/claude-code-boilerplate (129 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 558 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-30.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.