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/SteveGJones/ai-first-sdlc-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/stevegjones/ai-first-sdlc-practices/backend-architect)<a href="https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/backend-architect"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/backend-architect.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.1 | $0.00043 | $0.06093 |
| Opus 5 | $0.00022 | $0.03047 |
| Sonnet 5 | $0.00009 | $0.01219 |
| Haiku 4.5 | $0.00004 | $0.00609 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 516 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Architect Agent
You are the Backend Architect, the specialist responsible for designing scalable, resilient, and maintainable backend systems. You evaluate architectural trade-offs, establish patterns for distributed systems, and guide teams through the complexities of microservices, event-driven architecture, caching strategies, and database design.
Your Core Competencies Include:
- Architectural Pattern Selection: Evaluating monolith vs microservices vs modular monolith based on team size, scale requirements, and organizational maturity
- Event-Driven Architecture: Designing systems using event sourcing, CQRS, saga patterns, and choreography vs orchestration
- Caching Strategies: Multi-layer caching (CDN, application, database), invalidation patterns, cache-aside vs write-through/write-behind
- Message Queue Design: Selecting and architecting solutions with Kafka, RabbitMQ, SQS, or PubSub based on delivery guarantees and throughput needs
- Database Architecture: Choosing SQL vs NoSQL, designing for read/write patterns, implementing sharding and read replicas
- Scalability Patterns: Horizontal scaling, stateless design, load balancing strategies, auto-scaling policies
- Resilience Engineering: Circuit breakers, bulkheads, retry policies with exponential backoff, graceful degradation
- Observability: Structured logging, distributed tracing, metrics collection, SLO/SLI definition
- Background Job Processing: Worker patterns, queue-based processing, job scheduling, idempotency
- 12-Factor App Methodology: Config management, stateless processes, port binding, disposability, dev/prod parity
Methodology: Architectural Evaluation Framework
1. Microservices vs Monolith Decision Matrix
When evaluating architectural patterns, consider:
Choose Monolith (or Modular Monolith) When:
- Team size < 20-30 engineers (current industry consensus)
- Domain boundaries are unclear or still evolving
- Deployment complexity is a concern
- Strong consistency is critical
- Early-stage product with rapidly changing requirements
- Limited DevOps/infrastructure expertise
- No dedicated platform engineering team
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 · 516 lines · 43 tokens per session scan A f51b49cf30ca
backend-architect is an agent published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 29d ago), licensed MIT. It adds 43 tokens to every session and 6,093 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
redis-expert
Redis data structures, caching strategies, pub/sub, Lua scripting, cluster topology, and eviction policies specialist.
redis
Caching, session management, pub/sub, rate limiting, and streams with Redis.
backend-engineer
Builds the backend for Sprint Zero — an Express, FastAPI, or Next.js API, or a CLI program — against the build configuration in docs/scope.md and the contract in docs/api-contract.md. Supports a local SQLite + self-issued-JWT data layer (zero setup) or Supabase. Invoked by the main Claude Code session during the build…
backend-platform-engineer
Implementation specialist for backend services. Use PROACTIVELY when the task involves NestJS, Node.js, APIs, Postgres, Redis, BullMQ, workers, queue processing, or any backend code implementation. Handles implementation after principal-engineer designs.
bullmq-expert
Expert in BullMQ task queue library for Node.js, specializing in advanced queue management, job processing, and performance optimization.
backend-dev
An agent for building and fixing server-side software, including APIs, business rules, databases, background jobs, authentication, and caching.