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/florianbruniaux/ccboard/backend-architectgit clone --depth 1 https://github.com/FlorianBruniaux/ccboardWrote 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/florianbruniaux/ccboard/backend-architect)<a href="https://agentmods.dev/agents/florianbruniaux/ccboard/backend-architect"><img src="https://agentmods.dev/badge/agents/florianbruniaux/ccboard/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 | $0.00019 | $0.00455 |
| Opus 5 | $0.00010 | $0.00228 |
| Sonnet 5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
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 5d 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.
This is a copy
84% identical to backend-architect — 6 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.
What it actually says
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.
- 5d ago First seen · 53 lines · 19 tokens per session scan A 275f88ee21ba
backend-architect is an agent published in the GitHub repository FlorianBruniaux/ccboard (94 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 455 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to backend-architect, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
repo-research-analyst
Note: The current year is 2026. Use this when searching for recent documentation and patterns.
gsd-project-researcher
Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
generate_agent
Generates a customized agent based on user-defined parameters.
lead
Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.
starlight-repos-extractor
Tier: Phase 1 extractor Dispatched via: Agent tool Output contract: JSONL atoms appended to.
gsd-debugger
Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd:debug orchestrator.