backend-architect

An agent profile for designing server-side software, including APIs, databases, and larger system structures. It covers common choices such as REST or GraphQL APIs, SQL or NoSQL databases, authentication, caching, and service boundaries.

In plain words
What is it for?
Use it to design APIs, database schemas, authentication, caching, microservices, message queues, and other backend architecture.
Why use it?
It provides a broad checklist for making backend systems secure, maintainable, and able to handle growth. This helps avoid overlooking concerns such as error handling, permissions, indexes, or data migrations.

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/ccplugins/awesome-claude-code-plugins/backend-architect
Clone the repo
git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins
Per session 287 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 original No closer match found 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.00287 $0.01043
Opus 5 $0.00143 $0.00522
Sonnet 5 $0.00057 $0.00209
Haiku 4.5 $0.00029 $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

Copies of this mod

3 near-identical copies found in the catalogue:

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.

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.

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 ccplugins/awesome-claude-code-plugins (929 stars, last pushed 20d ago), licensed Apache-2.0. It adds 287 tokens to every session and 1,043 once invoked, about $0.0014 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.

Related

Other agents, from other repositories

e2e-test-agent

E2E test agent for validation.

alex-feel/claude-code-toolbox · 13 tokens

confluence-fetcher

ユーザーが Confluence ページの情報取得を依頼したとき、または Confluence URL を言及したときに使用する。 Context: ユーザーが Confluence URL を共有 user: "https://example.atlassian.net/wiki/spaces/DEV/pages/123/Guide この Wiki の内容を教えて" assistant: "confluence-fetcher エージェントを使用して Confluence ページの情報を取得します" ユーザーが Confluence URL を言及しているため、プロアクティブに confluence-fetcher…

lc-semba-ryuichiro/semba-claude-plugins · 437 tokens

image-optimizer

ユーザーが画像の WebP 変換や最適化を依頼したときに使用する。 Context: ユーザーが画像ディレクトリの最適化を依頼 user: "assets/images の画像を最適化して" assistant: "image-optimizer エージェントを使用して画像を分析し、最適化を実行します" ユーザーが画像の最適化を依頼しているため、image-optimizer エージェントを使用する。 Context: ユーザーが WebP 変換を依頼 user: "このディレクトリの PNG を WebP に変換して" assistant: "image-optimizer エージェントで PNG ファイルを WebP…

lc-semba-ryuichiro/semba-claude-plugins · 401 tokens

jira-fetcher

ユーザーが Jira 課題の情報取得を依頼したとき、または Jira URL を言及したときに使用する。 Context: ユーザーが Jira URL を共有 user: "https://example.atlassian.net/browse/PROJ-123 この課題の内容を教えて" assistant: "jira-fetcher エージェントを使用して Jira 課題 PROJ-123 の情報を取得します" ユーザーが Jira URL を言及しているため、プロアクティブに jira-fetcher エージェントを使用する。 Context: ユーザーが Jira 課題の取得を依頼 user: "PROJ-123…

lc-semba-ryuichiro/semba-claude-plugins · 443 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

program-manager

Proactively use for comprehensive Linear project management, release planning, dependency analysis, and project reorganization. Specialist for managing complex issue hierarchies, multi-release roadmaps, and cross-team dependencies.

memyselfandm/cconami · 42 tokens