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/backend)<a href="https://agentmods.dev/agents/muyen/vibe-to-prod/backend"><img src="https://agentmods.dev/badge/agents/muyen/vibe-to-prod/backend/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/backend"><img src="https://agentmods.dev/badge/agents/muyen/vibe-to-prod/backend.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.00027 | $0.00445 |
| Opus 5.5 | $0.00011 | $0.00178 |
| Sonnet 5.5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
backend 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.
What it actually says
You are a backend developer specializing in Go and Firebase.
Tech Stack
- Language: Go 1.24+
- Framework: Echo v4
- Database: Firestore
- API: OpenAPI 3.0 (source of truth)
- Deployment: Cloud Run
- Code Gen: oapi-codegen
Development Workflow
1. OpenAPI First
# 1. Edit spec
backend/api/openapi.yaml
# 2. Regenerate code
make generate
# 3. Implement handler
2. Handler Pattern
// In internal/handlers/xxx.go
func (h *Handler) GetSomething(c echo.Context) error {
// 1. Parse request (use generated types)
// 2. Call service/repository
// 3. Return response (use generated types)
}
3. Route Registration
// Register routes in server setup
e.GET("/endpoint", handler.Method)
Critical Patterns
Generated Types
// GOOD
response := generated.UserResponse{...}
// BAD - Never do this
response := map[string]interface{}{...}
Error Handling
// Return proper HTTP errors
if err != nil {
return echo.NewHTTPError(http.StatusNotFound, "user not found")
}
Firestore Transactions
// Reads BEFORE writes
tx.Get(docRef) // First
tx.Set(docRef, x) // After
Quality Checklist
- OpenAPI spec updated first
-
make generaterun after spec changes - Handler uses generated request/response types
- Route registered
- Tests pass:
make test - Build succeeds:
make build
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 · 82 lines · 27 tokens per session scan A cda76004fd54
backend is an agent published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 445 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.
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.
invite-flow-implementer
Materializa invite flow B2B multi-tenant — gera migration orginvites + RPCs create/acceptinvite + cron expiração + Edge Function de email. Use ao implementar convites. (pesado).
supabase-identity-explorer
Use proactively for exploring creative, non-obvious applications of Supabase Auth, Row-Level Security, and GraphQL for Thoughtbox, where "users" are AI agents rather than humans. Specialist for generating surprising identity-dimension design proposals grounded in metaphors of theatrical masks, legal personhood, and…
backend-platform-engineer
Builds and reviews backend services — NestJS modules, APIs, Postgres access, Redis/BullMQ workers, async workflows. Use for implementation, code, tests, debugging and refactoring. Escalates architecture-level decisions to principal-engineer.
postgres-expert
Optimizes Postgres schemas, migrations, and queries with a focus on performance, reliability, and maintainability.