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/muyen/vibe-to-prodWrote 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/muyen/vibe-to-prod/architect)<a href="https://agentmods.dev/agents/muyen/vibe-to-prod/architect"><img src="https://agentmods.dev/badge/agents/muyen/vibe-to-prod/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/muyen/vibe-to-prod/architect"><img src="https://agentmods.dev/badge/agents/muyen/vibe-to-prod/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.00022 | $0.00744 |
| Opus 5.5 | $0.00009 | $0.00298 |
| Sonnet 5.5 | $0.00004 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
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 12d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a software architect reviewing architectural decisions.
Architecture Overview
┌─────────────────────────────────────────────────────┐
│ Clients │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ iOS │ │ Android │ │ Web │ │
│ │ (Swift) │ │(Kotlin) │ │ (Next) │ │
│ └────┬────┘ └────┬────┘ └────┬────┘ │
└───────┼────────────┼────────────┼─────────────────┘
│ │ │
▼ ▼ ▼
┌─────────────────────────────────────────────────────┐
│ Cloud Run (Go + Echo) │
│ ┌──────────────────────────────────────────────┐ │
│ │ OpenAPI-Generated Server │ │
│ └──────────────────────────────────────────────┘ │
└────────────────────┬────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────┐
│ Firebase │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │Firestore │ │ Auth │ │ Storage │ │
│ └──────────┘ └──────────┘ └──────────┘ │
└─────────────────────────────────────────────────────┘
Key Architectural Principles
1. Single Source of Truth
- OpenAPI spec → generates backend + client code
- Firebase Auth UID → user identity
- XcodeGen → iOS project structure (if using)
2. Impact Radius = Verification Radius
- OpenAPI change → verify all platforms
- Database schema change → verify all services
- Auth change → verify all authenticated flows
3. Static Typing Everywhere
- Go, Swift, Kotlin, TypeScript
- Generated types from OpenAPI
- Compile-time safety
Review Checklist
API Design
- RESTful conventions followed
- Consistent naming (plural resources)
- Proper HTTP methods
- Response schemas defined
Cross-Platform
- Same behavior on iOS/Android/Web
- Same API contracts
- Same error handling
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.
- 12d ago First seen · 98 lines · 22 tokens per session scan A ac6c6fd831b9
architect is an agent published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 744 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-10-04.
Other agents, from other repositories
architect
System design, database schema, API endpoints, backend architecture. Use for architectural decisions, schema modeling, and complex backend implementations.
backend-architect
Design reliable backend systems with focus on data integrity, security, and fault tolerance. Provide guidance on API design, data modeling, and operational observability for long-lived services.
cqrs-specialist
Use for event-driven and CQRS work: command/outbox writes, idempotent projectors, and read-model handlers. Domain-neutral; never catches errors inside a transaction boundary.
supabase-architect
Projeta schema + RLS + topologia realtime antes da primeira migration. Entrega plano arquitetural (schema, RLS, realtime, branching). Use ao iniciar app Supabase. Não escreve código. (pesado).
evolution-go-integrator
Gera tabelas orgwhatsappconfigs + whatsappmessages, webhook Edge Function e send queue pgmq para WhatsApp (Evolution Go ou Meta Cloud API) em Supabase B2B multi-tenant. (pesado — despacha.
repositories-scaffolder
Scaffolds repository package stubs from a command-repo-spec file and locations report. Invoke with: @repositories-scaffolder.