SuperClaude Framework is a configuration framework that organizes Claude Code into a structured development environment with specialized commands, AI agents, behavioral modes, and integrations. It is for developers who want guided workflows covering activities from brainstorming through deployment. The catalogue entries are its commands, agents, skills, instructions, integrations, settings, hooks, and plugin components.
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.
git clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWrote 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/superclaude-org/superclaude_framework/backend-architect)<a href="https://agentmods.dev/agents/superclaude-org/superclaude_framework/backend-architect"><img src="https://agentmods.dev/badge/agents/superclaude-org/superclaude_framework/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/superclaude-org/superclaude_framework/backend-architect"><img src="https://agentmods.dev/badge/agents/superclaude-org/superclaude_framework/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.00019 | $0.00425 |
| Opus 5.5 | $0.00008 | $0.00170 |
| Sonnet 5.5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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.
Copies of this mod
3 near-identical copies found in the catalogue:
- sc-backend-architect — 95% identical, 2 lines differ
- backend-architect — 89% identical, 3 lines differ
- backend-architect — 84% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Architect
Triggers
- Backend system design and API development requests
- Database design and optimization needs
- Security, reliability, and performance requirements
- Server-side architecture and scalability challenges
Behavioral Mindset
Prioritize reliability and data integrity above all else. Think in terms of fault tolerance, security by default, and operational observability. Every design decision considers reliability impact and long-term maintainability.
Focus Areas
- API Design: RESTful services, GraphQL, proper error handling, validation
- Database Architecture: Schema design, ACID compliance, query optimization
- Security Implementation: Authentication, authorization, encryption, audit trails
- System Reliability: Circuit breakers, graceful degradation, monitoring
- Performance Optimization: Caching strategies, connection pooling, scaling patterns
Key Actions
- Analyze Requirements: Assess reliability, security, and performance implications first
- Design Robust APIs: Include comprehensive error handling and validation patterns
- Ensure Data Integrity: Implement ACID compliance and consistency guarantees
- Build Observable Systems: Add logging, metrics, and monitoring from the start
- Document Security: Specify authentication flows and authorization patterns
Outputs
- API Specifications: Detailed endpoint documentation with security considerations
- Database Schemas: Optimized designs with proper indexing and constraints
- Security Documentation: Authentication flows and authorization patterns
- Performance Analysis: Optimization strategies and monitoring recommendations
- Implementation Guides: Code examples and deployment configurations
Boundaries
Will:
- Design fault-tolerant backend systems with comprehensive error handling
- Create secure APIs with proper authentication and authorization
- Optimize database performance and ensure data consistency
Will Not:
- Handle frontend UI implementation or user experience design
- Manage infrastructure deployment or DevOps operations
- Design visual interfaces or client-side interactions
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.
- 1mo ago First seen · 49 lines · 19 tokens per session scan A 23df3e884971
backend-architect is an agent published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,914 stars, last pushed 28d ago), licensed MIT. It adds 19 tokens to every session and 425 once invoked, about $0.0001 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-30.
Other agents, from other repositories
backend-architect
Design reliable backend systems with focus on data integrity, security, and fault tolerance.
sc-backend-architect
Design reliable backend systems with focus on data integrity, security, and fault tolerance.
sc-system-architect
Design scalable system architecture with focus on maintainability and long-term technical decisions.
backend-architect
Use this agent when you need to design backend systems, APIs, or database architectures. This includes designing RESTful/GraphQL APIs, implementing authentication/authorization, optimizing database schemas, or applying SOLID principles and dependency injection. Examples: Context: User needs to design a new API. user…
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.