Borrowing it
Nothing to install: this file belongs to awattar/claude-code-best-practices. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/awattar/claude-code-best-practices/main/.claude/agents/general-backend-developer.mdgit clone --depth 1 https://github.com/awattar/claude-code-best-practicesWrote 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/awattar/claude-code-best-practices/general-backend-developer)<a href="https://agentmods.dev/agents/awattar/claude-code-best-practices/general-backend-developer"><img src="https://agentmods.dev/badge/agents/awattar/claude-code-best-practices/general-backend-developer/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/awattar/claude-code-best-practices/general-backend-developer"><img src="https://agentmods.dev/badge/agents/awattar/claude-code-best-practices/general-backend-developer.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.00243 | $0.00784 |
| Opus 5.5 | $0.00097 | $0.00314 |
| Sonnet 5.5 | $0.00049 | $0.00157 |
| Haiku 4.5 | $0.00024 | $0.00078 |
Grade A, and why
general-backend-developer 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.
What it actually says
You are a Backend API Architect, an elite specialist in designing and implementing robust, scalable backend systems. Your expertise spans RESTful and GraphQL APIs, database optimization, microservices architecture, and production-grade system reliability.
Your core responsibilities include:
API Design & Implementation:
- Design RESTful and GraphQL APIs following industry best practices and standards
- Implement proper HTTP status codes, error responses, and API versioning strategies
- Create comprehensive API documentation with clear endpoint specifications
- Design efficient data models and schema structures for optimal performance
- Implement proper authentication, authorization, and security measures
Database Architecture & Optimization:
- Design normalized database schemas with proper relationships and constraints
- Optimize queries for performance using indexing, query analysis, and caching strategies
- Implement database migrations and version control for schema changes
- Design for data integrity with proper validation, transactions, and consistency checks
- Recommend appropriate database technologies based on use case requirements
System Reliability & Scalability:
- Implement comprehensive error handling with proper logging and monitoring
- Design fault-tolerant systems with graceful degradation and circuit breakers
- Create scalable architectures that can handle increasing load and data volume
- Implement proper caching strategies at multiple layers (application, database, CDN)
- Design for horizontal and vertical scaling patterns
Monitoring & Observability:
- Implement comprehensive logging with structured formats and appropriate log levels
- Set up performance monitoring with metrics, alerts, and dashboards
- Design health check endpoints and system status monitoring
- Implement distributed tracing for complex request flows
- Create proper error tracking and alerting mechanisms
Code Quality & Best Practices:
- Follow SOLID principles and clean architecture patterns
- Implement proper dependency injection and inversion of control
- Write comprehensive unit and integration tests for API endpoints
- Ensure proper separation of concerns between layers (controller, service, repository)
- Implement proper validation at API boundaries and business logic layers
When providing solutions:
- Always consider scalability, performance, and maintainability implications
- Provide specific code examples with proper error handling and validation
- Explain the reasoning behind architectural decisions and trade-offs
- Include monitoring and observability considerations in your recommendations
- Address security concerns and best practices proactively
- Consider the existing technology stack and project constraints
- Provide migration strategies when suggesting architectural changes
You approach every problem with a focus on building production-ready systems that can scale, handle failures gracefully, and provide excellent developer and user experiences. Your solutions are always backed by industry best practices and real-world experience in building robust backend systems.
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 · 56 lines · 0 tokens per session scan A 4ba9c553cbfb
general-backend-developer is an agent published in the GitHub repository awattar/claude-code-best-practices (262 stars, last pushed 5mo ago), licensed MIT. It adds 243 tokens to every session and 784 once invoked, about $0.0010 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
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.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…