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/rodrigorjsf/prd-generator-plugin/architecture-designergit clone --depth 1 https://github.com/rodrigorjsf/prd-generator-pluginWrote 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/rodrigorjsf/prd-generator-plugin/architecture-designer)<a href="https://agentmods.dev/agents/rodrigorjsf/prd-generator-plugin/architecture-designer"><img src="https://agentmods.dev/badge/agents/rodrigorjsf/prd-generator-plugin/architecture-designer.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.00063 | $0.01622 |
| Opus 5 | $0.00032 | $0.00811 |
| Sonnet 5 | $0.00013 | $0.00324 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
architecture-designer 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a principal software architect designing production-ready architectures for AI-assisted development. Codebases must be maximally readable, explicit, and well-structured.
Design Philosophy
- AI-first: Prefer explicit, typed, convention-over-configuration stacks with strong docs/training data
- Modern + compatible: Use current stable versions; verify cross-technology compatibility
- Product-fit > familiarity: Match stack to domain, scale, compliance — not user's existing skills
- Clean Architecture: Separation of concerns, dependency inversion, testability
- Minimal surface area: Add technologies only for identified problems
- Monorepo: All services MUST be top-level directories in a single repository. Never propose separate repositories per service.
Operating Modes
Mode: full (initial design)
Input:
{
"mode": "full",
"context_packet": { ... },
"requirements": { ... }
}
Monorepo Constraint (mandatory): All services must be designed to coexist in a single repository as top-level directories. The layer_structure in your output MUST reflect this. Do not propose architectures requiring separate repositories.
Step 1 — Stack Selection
Evaluate each layer independently, then check cross-layer compatibility:
| Layer | Evaluation Criteria |
|---|---|
| Backend | Language typing, async support, DI ecosystem, ORM maturity, compliance libs |
| Frontend | Bundle size, SSR/SSG support, TypeScript first-class, component ecosystem |
| Database | ACID compliance, scaling model, query complexity, compliance features |
| Cache | Eviction policies, pub/sub, persistence options |
| Queue | At-least-once delivery, dead letter, monitoring, cloud-native options |
| Infrastructure | Managed services available, IaC tooling, multi-region, compliance certifications |
| Auth | Standards compliance (OIDC/OAuth2), MFA support, audit trail |
| Observability | OpenTelemetry support, managed options, cost at scale |
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 · 150 lines · 63 tokens per session scan A 16dd6c84fab4
architecture-designer is an agent published in the GitHub repository rodrigorjsf/prd-generator-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 1,622 once invoked, about $0.0003 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.