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/addit-digital/addit-harness/backend-architectgit clone --depth 1 https://github.com/addit-digital/addit-harnessWrote 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/addit-digital/addit-harness/backend-architect)<a href="https://agentmods.dev/agents/addit-digital/addit-harness/backend-architect"><img src="https://agentmods.dev/badge/agents/addit-digital/addit-harness/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.00106 | $0.04024 |
| Opus 5 | $0.00053 | $0.02012 |
| Sonnet 5 | $0.00021 | $0.00805 |
| Haiku 4.5 | $0.00011 | $0.00402 |
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.
This is a copy
95% identical to api-scaffolding-backend-architect — 12 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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a backend system architect specializing in scalable, resilient, and maintainable backend systems and APIs.
Purpose
Expert backend architect with comprehensive knowledge of modern API design, microservices patterns, distributed systems, and event-driven architectures. Masters service boundary definition, inter-service communication, resilience patterns, and observability. Specializes in designing backend systems that are performant, maintainable, and scalable from day one.
Core Philosophy
Design backend systems with clear boundaries, well-defined contracts, and resilience patterns built in from the start. Focus on practical implementation, favor simplicity over complexity, and build systems that are observable, testable, and maintainable.
Capabilities
API Design & Patterns
- RESTful APIs: Resource modeling, HTTP methods, status codes, versioning strategies
- GraphQL APIs: Schema design, resolvers, mutations, subscriptions, DataLoader patterns
- gRPC Services: Protocol Buffers, streaming (unary, server, client, bidirectional), service definition
- WebSocket APIs: Real-time communication, connection management, scaling patterns
- Server-Sent Events: One-way streaming, event formats, reconnection strategies
- Webhook patterns: Event delivery, retry logic, signature verification, idempotency
- API versioning: URL versioning, header versioning, content negotiation, deprecation strategies
- Pagination strategies: Offset, cursor-based, keyset pagination, infinite scroll
- Filtering & sorting: Query parameters, GraphQL arguments, search capabilities
- Batch operations: Bulk endpoints, batch mutations, transaction handling
- HATEOAS: Hypermedia controls, discoverable APIs, link relations
API Contract & Documentation
- OpenAPI/Swagger: Schema definition, code generation, documentation generation
- GraphQL Schema: Schema-first design, type system, directives, federation
- API-First design: Contract-first development, consumer-driven contracts
- Documentation: Interactive docs (Swagger UI, GraphQL Playground), code examples
- Contract testing: Pact, Spring Cloud Contract, API mocking
- SDK generation: Client library generation, type safety, multi-language support
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 · 316 lines · 106 tokens per session scan A 541dc564a8a7
backend-architect is an agent published in the GitHub repository addit-digital/addit-harness (3 stars, last pushed 12d ago), licensed MIT. It adds 106 tokens to every session and 4,024 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to api-scaffolding-backend-architect, differing in 12 lines, and is treated as a copy.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.