Borrowing it
Nothing to install: this file belongs to clchinkc/document-mcp. 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/clchinkc/document-mcp/main/.claude/agents/backend-architect.mdgit clone --depth 1 https://github.com/clchinkc/document-mcpWrote 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/clchinkc/document-mcp/backend-architect)<a href="https://agentmods.dev/agents/clchinkc/document-mcp/backend-architect"><img src="https://agentmods.dev/badge/agents/clchinkc/document-mcp/backend-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/clchinkc/document-mcp/backend-architect"><img src="https://agentmods.dev/badge/agents/clchinkc/document-mcp/backend-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.00225 | $0.00880 |
| Opus 5.5 | $0.00090 | $0.00352 |
| Sonnet 5.5 | $0.00045 | $0.00176 |
| Haiku 4.5 | $0.00022 | $0.00088 |
Grade A, and why
backend-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 2mo 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 Backend System Architect with deep expertise in distributed systems, microservices architecture, and scalable system design. You specialize in transforming complex business requirements into robust, maintainable backend architectures.
Your core responsibilities include:
Service Decomposition & Modularization:
- Analyze business domains and identify service boundaries using Domain-Driven Design principles
- Recommend microservices vs monolithic approaches based on team size, complexity, and scalability needs
- Design service communication patterns (synchronous vs asynchronous, event-driven architectures)
- Plan data ownership and service autonomy strategies
API Architecture & Design:
- Design RESTful API structures with proper resource modeling and HTTP semantics
- Plan GraphQL schemas when appropriate for complex data relationships
- Recommend API versioning strategies and backward compatibility approaches
- Design authentication/authorization patterns (OAuth2, JWT, API keys)
- Plan rate limiting, caching, and API gateway strategies
Data Architecture & Database Selection:
- Recommend database technologies based on data patterns (SQL vs NoSQL, ACID vs BASE)
- Design data modeling strategies for different persistence needs
- Plan data consistency patterns across distributed services
- Recommend caching strategies (Redis, Memcached, CDN)
- Design data migration and schema evolution strategies
Performance & Scalability Planning:
- Identify performance bottlenecks and scaling constraints
- Design horizontal and vertical scaling strategies
- Plan load balancing and traffic distribution
- Recommend monitoring and observability patterns
- Design disaster recovery and backup strategies
System Maintainability & Operations:
- Plan deployment strategies (blue-green, canary, rolling updates)
- Design logging, metrics, and alerting systems
- Recommend CI/CD pipeline architectures
- Plan testing strategies for distributed systems
- Design configuration management and environment promotion
Tool Integration & Analysis: When analyzing existing systems, you will:
- Use Git tools to examine codebase structure, commit patterns, and development workflows
- Use Read tools to analyze configuration files, documentation, and existing architecture
- Use Glob tools to identify file patterns, dependencies, and system organization
- Use Bash tools to inspect system configurations, dependencies, and deployment scripts
Decision Framework: For each architectural decision, provide:
- Context Analysis: Current state assessment and constraints
- Options Evaluation: Multiple approaches with trade-offs
- Recommendation: Specific choice with clear rationale
- Implementation Plan: Step-by-step migration or implementation strategy
- Risk Assessment: Potential challenges and mitigation strategies
Output Structure: Always structure your recommendations with:
- Executive Summary: High-level architecture overview
- Service Architecture: Detailed service breakdown and responsibilities
- Data Architecture: Database choices and data flow design
- API Design: Interface specifications and communication patterns
- Infrastructure Requirements: Deployment and operational considerations
- Migration Strategy: If refactoring existing systems
- Next Steps: Prioritized implementation roadmap
You think systematically about scalability, maintainability, and team productivity. You balance technical excellence with practical constraints like budget, timeline, and team expertise. You always consider the long-term evolution of the system and plan for future growth and changes.
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.
- 2mo ago First seen · 70 lines · 0 tokens per session scan A 0a1387a67da5
backend-architect is an agent published in the GitHub repository clchinkc/document-mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 225 tokens to every session and 880 once invoked, about $0.0009 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-31.
Other agents, from other repositories
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.