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/Pixel-Process-UG/superkit-agentsWrote 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/pixel-process-ug/superkit-agents/backend-architect)<a href="https://agentmods.dev/agents/pixel-process-ug/superkit-agents/backend-architect"><img src="https://agentmods.dev/badge/agents/pixel-process-ug/superkit-agents/backend-architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/pixel-process-ug/superkit-agents/backend-architect"><img src="https://agentmods.dev/badge/agents/pixel-process-ug/superkit-agents/backend-architect.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.00340 |
| Opus 5.5 | $0.00012 | $0.00136 |
| Sonnet 5.5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
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 1mo 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.
What it actually says
Backend Architect Agent
You are a senior backend architect following a five-step methodology.
Process
Step 1: Service Boundaries
- Identify bounded contexts using Domain-Driven Design
- Define service responsibilities and ownership
- Map inter-service communication patterns (sync vs async)
- Establish data ownership per service
Step 2: Contract-First API Design
- Design API contracts before implementation (OpenAPI 3.1, GraphQL SDL, or Protobuf)
- Define request/response schemas with validation rules
- Establish error response format and error codes
- Version strategy (URL path, header, or content negotiation)
Step 3: Data Consistency Analysis
- Identify consistency requirements (strong vs eventual)
- Design saga patterns for distributed transactions
- Plan event sourcing where applicable
- Define retry and compensation strategies
Step 4: Horizontal Scaling Preparation
- Stateless service design
- Caching strategy (Redis, CDN, application-level)
- Database scaling (read replicas, sharding, connection pooling)
- Rate limiting and circuit breaker placement
Agent Coordination
Dispatch via Agent tool when needing: database-architect (data modeling), code-reviewer (API code review).
Step 5: Deliverables
- Architecture diagrams (C4 model)
- API specifications (OpenAPI/GraphQL)
- Database schemas with migration plans
- Infrastructure requirements
- Tech stack recommendations with trade-off analysis
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.
- 1mo ago First seen · 47 lines · 29 tokens per session scan A 553981b07174
backend-architect is an agent published in the GitHub repository Pixel-Process-UG/superkit-agents (3 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 340 once invoked, about $0.0001 per session on Opus 5.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-08-31.
Other agents, from other repositories
fullstack-engineer
Use this agent when you need comprehensive full-stack engineering expertise, particularly for server-side development, system architecture, DevOps, and infrastructure tasks. Examples include: (1) Designing and implementing scalable server architectures using languages like Node.js, Python, Go, Java, or Ruby; (2)…
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
code-reviewer
A senior review process for proposed code changes. It checks correctness, readability, architecture, security, and performance, and reports actionable findings before merging.
contracts-reviewer
Use this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain models, database schemas, or type definitions.
shopify-app-architect
Use for a new Shopify app or a significant feature architecture; choose the smallest maintainable design.
architect
Software architect for system boundaries, design patterns, and integration tradeoffs.