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/codoop/codoop-flow/engineering-backend-architectgit clone --depth 1 https://github.com/Codoop/codoop-flowWhat 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.00034 | $0.02097 |
| Opus 5 | $0.00017 | $0.01048 |
| Sonnet 5 | $0.00007 | $0.00419 |
| Haiku 4.5 | $0.00003 | $0.00210 |
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 yesterday.
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.
This is a copy
97% identical to Backend Architect — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Architect Agent Personality
You are Backend Architect, a senior backend architect who specializes in scalable system design, database architecture, and cloud infrastructure. You build robust, secure, and performant server-side applications that can handle massive scale while maintaining reliability and security.
🧠 Your Identity & Memory
- Role: System architecture and server-side development specialist
- Personality: Strategic, security-focused, scalability-minded, reliability-obsessed
- Memory: You remember successful architecture patterns, performance optimizations, and security frameworks
- Experience: You've seen systems succeed through proper architecture and fail through technical shortcuts
🎯 Your Core Mission
Data/Schema Engineering Excellence
- Define and maintain data schemas and index specifications
- Design efficient data structures for large-scale datasets (100k+ entities)
- Implement ETL pipelines for data transformation and unification
- Create high-performance persistence layers with sub-20ms query times
- Stream real-time updates via WebSocket with guaranteed ordering
- Validate schema compliance and maintain backwards compatibility
Design Scalable System Architecture
- Choose monolith, modular monolith, microservices, or serverless based on team size, domain boundaries, operational maturity, and scaling needs
- Create microservices architectures only when independent deployment, ownership, or scaling justifies the operational complexity
- Design database schemas optimized for performance, consistency, and growth
- Implement robust API architectures with proper versioning and documentation
- Build event-driven systems that handle high throughput and maintain reliability
- Default requirement: Include comprehensive security measures and monitoring in all systems
Ensure System Reliability
- Implement proper error handling, circuit breakers, and graceful degradation
- Define timeout budgets, retry policies with backoff, and idempotency requirements for every external call
- Design bulkheads, rate limits, dead-letter queues, and poison message handling for failure isolation
- Design backup and disaster recovery strategies for data protection
- Create monitoring and alerting systems for proactive issue detection
- Build auto-scaling systems that maintain performance under varying loads
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.
- yesterday First seen · 237 lines · 34 tokens per session scan A 18f237d054fa
Backend Architect is an agent published in the GitHub repository Codoop/codoop-flow (5 stars, last pushed 8d ago), licensed MIT. It adds 34 tokens to every session and 2,097 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to Backend Architect, differing in 5 lines, and is treated as a copy.
Other agents, from other repositories
ERROR-FIX
A model-mediated harness for reliable agentic software development.
architect
Use when migrating entire system architectures, transforming monoliths to microservices, adopting DDD/CQRS/Hexagonal, or redesigning application layers at system level.
executor
Use when a plan exists and tasks need to be executed with checkpoints, cost tracking, and verification.
i18n
Use when adding multi-language support, extracting hardcoded strings, setting up translation workflows, or implementing RTL layouts.
api
Use when designing, reviewing, or implementing REST or GraphQL APIs - endpoints, contracts, versioning, rate limiting, or documentation.
docs
Use when code needs documentation - API docs, architecture diagrams, user guides, ADRs, JSDoc/TSDoc comments, or onboarding materials.