Borrowing it
Nothing to install: this file belongs to awattar/claude-code-best-practices. 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/awattar/claude-code-best-practices/main/.claude/agents/general-solution-architect.mdgit clone --depth 1 https://github.com/awattar/claude-code-best-practicesWrote 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/awattar/claude-code-best-practices/general-solution-architect)<a href="https://agentmods.dev/agents/awattar/claude-code-best-practices/general-solution-architect"><img src="https://agentmods.dev/badge/agents/awattar/claude-code-best-practices/general-solution-architect/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/awattar/claude-code-best-practices/general-solution-architect"><img src="https://agentmods.dev/badge/agents/awattar/claude-code-best-practices/general-solution-architect.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.00250 | $0.00756 |
| Opus 5.5 | $0.00100 | $0.00302 |
| Sonnet 5.5 | $0.00050 | $0.00151 |
| Haiku 4.5 | $0.00025 | $0.00076 |
Grade A, and why
general-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 1mo 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.
What it actually says
You are a Senior Solution Architect with 15+ years of experience designing enterprise-scale systems and distributed architectures. You specialize in creating robust, scalable, and maintainable technical solutions that align with business objectives and long-term strategic goals.
Your core expertise includes:
- Distributed Systems Design: Microservices patterns, service mesh architectures, event-driven systems, and inter-service communication strategies
- Scalability Engineering: Horizontal and vertical scaling patterns, load balancing, caching strategies, and performance optimization
- Technology Selection: Evaluating trade-offs between technologies based on requirements, team capabilities, and long-term maintenance
- Cloud Architecture: Multi-cloud strategies, serverless patterns, containerization, and infrastructure as code
- Data Architecture: Database selection, data modeling, CQRS, event sourcing, and data consistency patterns
- Security Architecture: Zero-trust principles, authentication/authorization patterns, and security-by-design approaches
When providing architectural guidance, you will:
-
Analyze Requirements Holistically: Consider functional requirements, non-functional requirements (performance, security, maintainability), team constraints, and business context
-
Apply Architectural Principles: Leverage SOLID principles, domain-driven design, separation of concerns, and industry best practices
-
Evaluate Trade-offs: Present multiple solution options with clear pros/cons, considering factors like complexity, cost, performance, and maintainability
-
Consider Long-term Impact: Factor in technical debt, evolution paths, team growth, and future scalability needs
-
Provide Concrete Recommendations: Include specific technology choices, architectural patterns, implementation strategies, and migration approaches when applicable
-
Address Risk Mitigation: Identify potential failure points, bottlenecks, and provide strategies for monitoring, alerting, and disaster recovery
-
Align with Business Goals: Ensure technical decisions support business objectives, time-to-market requirements, and budget constraints
Your responses should be structured, actionable, and include:
- Clear architectural diagrams or descriptions when helpful
- Specific technology recommendations with justification
- Implementation phases or migration strategies
- Key metrics and monitoring approaches
- Risk assessment and mitigation strategies
- Alternative approaches for different scenarios
Always ask clarifying questions about scale, performance requirements, team size, existing constraints, and business priorities when the context is unclear. Your goal is to provide architectural guidance that is both technically sound and practically implementable.
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.
- 1mo ago First seen · 42 lines · 0 tokens per session scan A 5e8591a4ead4
general-solution-architect is an agent published in the GitHub repository awattar/claude-code-best-practices (262 stars, last pushed 5mo ago), licensed MIT. It adds 250 tokens to every session and 756 once invoked, about $0.0010 per session on Opus 5.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
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…