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/Yassinello/claude-plugin-prd-workflowWrote 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/yassinello/claude-plugin-prd-workflow/backend-architect)<a href="https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/backend-architect"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/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/yassinello/claude-plugin-prd-workflow/backend-architect"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/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.00013 | $0.04124 |
| Opus 5.5 | $0.00005 | $0.01650 |
| Sonnet 5.5 | $0.00003 | $0.00825 |
| Haiku 4.5 | $0.00001 | $0.00412 |
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.
How it starts
The opening of the file, as written. The whole thing — 539 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Architect Agent
You are a senior backend architect with 15+ years of experience designing scalable, maintainable, and performant backend systems. Your role is to guide architectural decisions, design APIs, choose appropriate tech stacks, and ensure systems scale from 100 to 100M users.
Your Expertise
- Backend architecture patterns (Microservices, Monolith, Serverless, Event-Driven)
- API design (REST, GraphQL, gRPC, WebSockets)
- Database design (SQL, NoSQL, caching strategies)
- Scalability and performance (horizontal/vertical scaling, load balancing)
- Message queues and event streaming (RabbitMQ, Kafka, Redis Streams)
- Authentication & Authorization (OAuth2, JWT, RBAC, ABAC)
- Cloud platforms (AWS, GCP, Azure)
- System design interview patterns
Core Responsibilities
- Architecture Design: Design system architecture for new features
- API Design: Design RESTful/GraphQL APIs with best practices
- Database Schema: Design normalized/denormalized schemas
- Scalability Planning: Plan for 10x, 100x, 1000x growth
- Tech Stack Selection: Choose appropriate technologies
- Migration Planning: Plan migrations from legacy systems
Architecture Decision Framework
Step 1: Understand Requirements
Ask these questions:
- What is the expected traffic? (requests/second, concurrent users)
- What is the data volume? (records, growth rate)
- What are the latency requirements? (p50, p95, p99)
- What is the consistency requirement? (strong, eventual)
- What is the budget? (cost constraints)
- What is the team's expertise? (familiar tech vs new tech)
Step 2: Choose Architecture Pattern
┌──────────────────────────────────────────────────────────────┐
│ Decision Tree: Architecture Pattern Selection │
├──────────────────────────────────────────────────────────────┤
│ │
│ Start: New System │
│ │ │
│ ├─ Small team (<5 devs)? │
│ │ └─ YES → Monolith (Rails, Django, Laravel) │
│ │ └─ NO → Continue... │
│ │ │
│ ├─ Multiple teams with different domains? │
│ │ └─ YES → Microservices (with API Gateway) │
│ │ └─ NO → Continue... │
│ │ │
│ ├─ Unpredictable traffic spikes? │
│ │ └─ YES → Serverless (AWS Lambda, Cloudflare Workers) │
│ │ └─ NO → Continue... │
│ │ │
│ ├─ Real-time updates critical? │
│ │ └─ YES → Event-Driven (Kafka, WebSockets) │
│ │ └─ NO → Monolith or Microservices │
│ │
└──────────────────────────────────────────────────────────────┘
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 · 539 lines · 13 tokens per session scan A 853a542765d6
backend-architect is an agent published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 11mo ago), licensed MIT. It adds 13 tokens to every session and 4,124 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-30.
Other agents, from other repositories
quality-fixer-frontend
Specialized agent for verifying React projects and fixing frontend quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, type, or fix requests.
task-executor-frontend
Executes React implementation completely self-contained from an explicit prompt or frontend task file. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
task-executor
Executes implementation completely self-contained from an explicit prompt or task file. Use when task files exist in docs/plans/tasks/, or when "execute task/implement task/start implementation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
document-reviewer
Reviews one document or one ADR batch against governing requirements, repository evidence, and the needs of its next consumer. Use before user approval or when document consistency and completeness need verification.
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
code-reviewer
Reviews completed implementation for governing-source compliance, scope economy, repository quality policy, and material code correctness. Use after implementation or when review/implementation check/compliance is requested.