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.
npx agentmods add agents/awattar/claude-code-best-practices/general-backend-developergit 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.svg" alt="Measured on agentmods" 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 | $0.00243 | $0.00784 |
| Opus 5 | $0.00121 | $0.00392 |
| Sonnet 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 4d 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.
- 4d 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 (250 stars, last pushed 3mo ago), licensed MIT. It adds 243 tokens to every session and 784 once invoked, about $0.0012 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.
Other agents, from other repositories
database-monitoring
Query and manage Datadog Database Monitoring (DBM) data, including database metrics, query performance, and DBM-specific monitors.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
db-performance-auditor
Audits a .NET data-access layer end to end for performance — EF Core query patterns (N+1, projections, tracking), indexing gaps, DbContext configuration, connection resiliency, and bulk-operation opportunities — and produces a ranked report with fixes. Use when the user wants a database/EF performance review of a…