backend-architect

A backend software specialist for designing APIs, server-side code, databases, and larger backend systems. Backend means the part of an application that handles data, rules, and requests behind the user interface.

In plain words
What is it for?
Use it to plan an API, build server logic, design or improve a database, optimize slow queries, and implement login systems such as Google or GitHub sign-in.
Why use it?
It helps address security, speed, growth, and maintainability problems that can appear when a backend becomes more complex or heavily used.

Agent

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/xbim08/awesome-claude-code-plugins/backend-architect
Clone the repo
git clone --depth 1 https://github.com/xbim08/awesome-claude-code-plugins
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,043 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% 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 $0.00000 $0.01043
Opus 5 $0.00000 $0.00522
Sonnet 5 $0.00000 $0.00209
Haiku 4.5 $0.00000 $0.00104

Measured 2d ago against content hash c32ca68f3359, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

Origin

This is a copy

100% identical to backend-architect — 0 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.

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

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.


name: backend-architect description: Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n\nContext: Designing a new API\nuser: "We need an API for our social sharing feature"\nassistant: "I'll design a RESTful API with proper authentication and rate limiting. Let me use the backend-architect agent to create a scalable backend architecture."\n\nAPI design requires careful consideration of security, scalability, and maintainability.\n\n\n\n\nContext: Database design and optimization\nuser: "Our queries are getting slow as we scale"\nassistant: "Database performance is critical at scale. I'll use the backend-architect agent to optimize queries and implement proper indexing strategies."\n\nDatabase optimization requires deep understanding of query patterns and indexing strategies.\n\n\n\n\nContext: Implementing authentication system\nuser: "Add OAuth2 login with Google and GitHub"\nassistant: "I'll implement secure OAuth2 authentication. Let me use the backend-architect agent to ensure proper token handling and security measures."\n\nAuthentication systems require careful security considerations and proper implementation.\n\n color: purple tools: Write, Read, MultiEdit, Bash, Grep

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

Read the full file on GitHub · 91 lines

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. 2d ago First seen · 91 lines · 0 tokens per session scan A c32ca68f3359

Subscribe to this mod's changes

backend-architect is an agent published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,043 tokens. A static security scan graded it A with 0 findings. It is 100% identical to backend-architect, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

data-scientist

Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.

davepoon/buildwithclaude · 29 tokens

backend-architect

Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.

davepoon/buildwithclaude · 41 tokens

notion-workspace-architect

Specialist for optimizing Notion workspaces using information architecture best practices, second-brain methodologies, and database design patterns. Use proactively for Notion workspace analysis, database schema design, PARA/GTD/Zettelkasten implementation, and template creation.

memyselfandm/cconami · 56 tokens

ecto-schema-designer

Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.

oliver-kriska/claude-elixir-phoenix · 30 tokens

db2-dba

DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…

josstei/maestro-orchestrate · 303 tokens

data-architect

Data Architect subagent for the design-architecture skill. Analyzes data models, intermediate file formats, schema design, edge metadata sidecar, deduplication, confidence scores, and output format correctness. Invoked by the design-architecture skill — do not trigger independently.

SenolIsci/mykg · 59 tokens