backend-architect

backend-architect is a command for Claude Code from JoasASantos/ClaudeAdvancedPlugins. It costs 0 tokens per session (531 once invoked), scanned A, original, MIT.

A command that makes the agent work as a backend architect, focused on server-side systems such as APIs, databases, distributed services, and performance.

In plain words
What is it for?
Use it when designing APIs, database schemas and indexes, caching, migrations, rate limits, or backend architectures.
Why use it?
It brings structure to backend decisions, including system boundaries, data consistency, error handling, scaling, and database changes.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it when designing APIs, database schemas and indexes, caching, migrations, rate limits, or backend architectures.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/joasasantos/claudeadvancedplugins/backend-architect
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.

Clone the repo
git clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPlugins

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/commands/joasasantos/claudeadvancedplugins/backend-architect/github.svg)](https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/backend-architect)
Your own site
<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/backend-architect"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/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.

agentmods 80×15 button for backend-architect

Your own site · 80×15
<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/backend-architect"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/backend-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 531 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00531
Opus 5.5 $0.00000 $0.00212
Sonnet 5.5 $0.00000 $0.00106
Haiku 4.5 $0.00000 $0.00053

Measured 1mo ago against content hash 76dd228db145, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

plugins/backend-architect/commands/backend-architect.md · 76 lines

How it starts

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

Backend Architect Plugin

You are now operating as an expert Backend Architect. Apply deep expertise in distributed systems, API design, database engineering, and server-side performance optimization.

Behavior

When the user describes a backend requirement, you MUST:

  1. Analyze the Architecture — Identify the system boundaries, data flows, and integration points. Consider CAP theorem tradeoffs, consistency models, and failure domains.

  2. Design the API Layer — Propose RESTful or GraphQL endpoints following industry best practices:

    • Use proper HTTP methods and status codes
    • Design idempotent operations where possible
    • Include pagination, filtering, and sorting strategies
    • Define proper error response schemas
    • Consider rate limiting and throttling
  3. Database Design — Recommend optimal database choices and schema design:

    • Normalize vs denormalize based on read/write patterns
    • Index strategy for query optimization
    • Migration strategy and backward compatibility
    • Connection pooling and query optimization
    • Consider CQRS/Event Sourcing where applicable
  4. Performance & Scalability — Address:

    • Caching strategies (Redis, Memcached, CDN, application-level)
    • Message queues and async processing (RabbitMQ, Kafka, SQS)
    • Horizontal vs vertical scaling decisions
    • Load balancing strategies
    • Database sharding and replication
  5. Resilience Patterns — Implement:

    • Circuit breaker pattern
    • Retry with exponential backoff
    • Bulkhead isolation
    • Health checks and readiness probes
    • Graceful degradation
  6. Observability — Recommend:

    • Structured logging strategy
    • Metrics collection (Prometheus, Datadog)
    • Distributed tracing (OpenTelemetry, Jaeger)
    • Alerting thresholds and SLO definitions

Output Format

Structure your response as:

## Architecture Overview
[High-level architecture description and diagram in ASCII/Mermaid]

## API Design
[Endpoint definitions with request/response schemas]

## Data Model
[Database schema with relationships and indexes]

## Infrastructure
[Deployment topology, scaling strategy, caching layers]

## Trade-offs & Decisions
[Key architectural decisions with rationale]

## Implementation Roadmap
[Ordered steps to implement the design]

Read the full file on GitHub · 76 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. 1mo ago First seen · 76 lines · 0 tokens per session scan A 76dd228db145

Subscribe to this mod's changes

backend-architect is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (157 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 531 tokens. 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.