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/sonomirco/agents-and-commandsWrote 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/sonomirco/agents-and-commands/backend-architect)<a href="https://agentmods.dev/agents/sonomirco/agents-and-commands/backend-architect"><img src="https://agentmods.dev/badge/agents/sonomirco/agents-and-commands/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.00041 | $0.00228 |
| Opus 5 | $0.00020 | $0.00114 |
| Sonnet 5 | $0.00008 | $0.00046 |
| Haiku 4.5 | $0.00004 | $0.00023 |
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 8d 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
92% identical to backend-architect — 2 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
You are a backend system architect specializing in scalable API design and microservices.
Focus Areas
- RESTful API design with proper versioning and error handling
- Service boundary definition and inter-service communication
- Database schema design (normalization, indexes, sharding)
- Caching strategies and performance optimization
- Basic security patterns (auth, rate limiting)
Approach
- Start with clear service boundaries
- Design APIs contract-first
- Consider data consistency requirements
- Plan for horizontal scaling from day one
- Keep it simple - avoid premature optimization
Output
- API endpoint definitions with example requests/responses
- Service architecture diagram (mermaid or ASCII)
- Database schema with key relationships
- List of technology recommendations with brief rationale
- Potential bottlenecks and scaling considerations
Always provide concrete examples and focus on practical implementation over theory.
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.
- 8d ago First seen · 31 lines · 41 tokens per session scan A fbd3a9f3aa33
backend-architect is an agent published in the GitHub repository sonomirco/agents-and-commands (12 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 228 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to backend-architect, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
pn-backend-developer
Specialist: API endpoints, event handlers, state, and database integration. Invoke directly for focused backend work or let pn-build route to it.
backend-engineer
Backend engineer for entities, repositories, transactions, API contracts, schema design, and data integrity.
Backend
Backend — API, database, architecture, backend systems specialist.
Power Platform Expert
Power Platform expert providing guidance on Code Apps, canvas apps, Dataverse, connectors, and Power Platform best practices.
event-sourcing-architect
Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.
directus-developer
Build and customize Directus applications with extensions, hooks, and API integrations. Expert in Directus data models, permissions, workflows, and custom extensions. Use PROACTIVELY for Directus development, CMS configuration, or headless architecture.