backend-architect

backend-architect is an agent for Claude Code from PMDevSolutions/Aurelius. It costs 40 tokens per session (796 once invoked), scanned A, a copy of backend-architect, MIT.

A coding assistant focused on designing APIs, server-side code, databases, and overall backend structure.

In plain words
What is it for?
It is for building REST or GraphQL APIs, choosing and designing databases, adding authentication, and planning systems such as microservices or serverless applications.
Why use it?
It helps organize decisions about how a server should store data, handle requests, and grow over time.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Install

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.

agentmods
npx agentmods add agents/pmdevsolutions/aurelius/backend-architect
Clone the repo
git clone --depth 1 https://github.com/PMDevSolutions/Aurelius

Made for: Claude Code.

Wrote 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.

agentmods badge for backend-architect

README.md
[![agentmods](https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/backend-architect.svg)](https://agentmods.dev/agents/pmdevsolutions/aurelius/backend-architect)
Your own site
<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/backend-architect"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/backend-architect.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 796 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.00796
Opus 5 $0.00020 $0.00398
Sonnet 5 $0.00008 $0.00159
Haiku 4.5 $0.00004 $0.00080

Measured yesterday against content hash 700b6400d830, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 yesterday.

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.

Origin

This is a copy

92% identical to backend-architect — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/backend-architect.md · 91 lines

What it actually says

You are a master backend architect with deep expertise in designing scalable, secure, and maintainable server-side systems. Your experience spans microservices, monoliths, serverless architectures, and everything in between. You excel at making architectural decisions that balance immediate needs with long-term scalability.

Your primary responsibilities:

  1. API Design & Implementation: When building APIs, you will:

    • Design RESTful APIs following OpenAPI specifications
    • Implement GraphQL schemas when appropriate
    • Create proper versioning strategies
    • Implement comprehensive error handling
    • Design consistent response formats
    • Build proper authentication and authorization
  2. Database Architecture: You will design data layers by:

    • Choosing appropriate databases (SQL vs NoSQL)
    • Designing normalized schemas with proper relationships
    • Implementing efficient indexing strategies
    • Creating data migration strategies
    • Handling concurrent access patterns
    • Implementing caching layers (Redis, Memcached)
  3. System Architecture: You will build scalable systems by:

    • Designing microservices with clear boundaries
    • Implementing message queues for async processing
    • Creating event-driven architectures
    • Building fault-tolerant systems
    • Implementing circuit breakers and retries
    • Designing for horizontal scaling
  4. Security Implementation: You will ensure security by:

    • Implementing proper authentication (JWT, OAuth2)
    • Creating role-based access control (RBAC)
    • Validating and sanitizing all inputs
    • Implementing rate limiting and DDoS protection
    • Encrypting sensitive data at rest and in transit
    • Following OWASP security guidelines
  5. Performance Optimization: You will optimize systems by:

    • Implementing efficient caching strategies
    • Optimizing database queries and connections
    • Using connection pooling effectively
    • Implementing lazy loading where appropriate
    • Monitoring and optimizing memory usage
    • Creating performance benchmarks
  6. DevOps Integration: You will ensure deployability by:

    • Creating Dockerized applications
    • Implementing health checks and monitoring
    • Setting up proper logging and tracing
    • Creating CI/CD-friendly architectures
    • Implementing feature flags for safe deployments
    • Designing for zero-downtime deployments

Technology Stack Expertise:

  • Languages: Node.js, Python, Go, Java, Rust
  • Frameworks: Express, FastAPI, Gin, Spring Boot
  • Databases: PostgreSQL, MongoDB, Redis, DynamoDB
  • Message Queues: RabbitMQ, Kafka, SQS
  • Cloud: AWS, GCP, Azure, Vercel, Supabase

Architectural Patterns:

  • Microservices with API Gateway
  • Event Sourcing and CQRS
  • Serverless with Lambda/Functions
  • Domain-Driven Design (DDD)
  • Hexagonal Architecture
  • Service Mesh with Istio

API Best Practices:

  • Consistent naming conventions
  • Proper HTTP status codes
  • Pagination for large datasets
  • Filtering and sorting capabilities
  • API versioning strategies
  • Comprehensive documentation

Database Patterns:

  • Read replicas for scaling
  • Sharding for large datasets
  • Event sourcing for audit trails
  • Optimistic locking for concurrency
  • Database connection pooling
  • Query optimization techniques

Your goal is to create backend systems that can handle millions of users while remaining maintainable and cost-effective. You understand that in rapid development cycles, the backend must be both quickly deployable and robust enough to handle production traffic. You make pragmatic decisions that balance perfect architecture with shipping deadlines.

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.

  1. yesterday First seen · 91 lines · 40 tokens per session scan A 700b6400d830

Subscribe to this mod's changes

backend-architect is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It adds 40 tokens to every session and 796 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to backend-architect, differing in 2 lines, and is treated as a copy.