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 skills add roedyrustam/vibes-plug --skill zero-to-prod-orchestratorgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/skills/roedyrustam/vibes-plug/zero-to-prod-orchestrator)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/zero-to-prod-orchestrator"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/zero-to-prod-orchestrator/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/skills/roedyrustam/vibes-plug/zero-to-prod-orchestrator"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/zero-to-prod-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.06046 |
| Opus 5 | $0.00028 | $0.03023 |
| Sonnet 5 | $0.00011 | $0.01209 |
| Haiku 4.5 | $0.00006 | $0.00605 |
Grade A, and why
zero-to-prod-orchestrator 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 6d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zero to Production Orchestrator (2026 Master Edition)
English
Orchestration & Integration
Connects and orchestrates with relevant domain skills like brainstorming, zero-to-prod-orchestrator, and project-context-mapper to ensure cohesive execution.
Overview
The Zero to Production Orchestrator is the ultimate master skill designed to orchestrate the entire vibes-plug ecosystem as a highly interconnected engineering swarm. By acting as the central conductor, it ensures that no sub-skill is executed in isolation. It guides fullstack developers through the complete software engineering lifecycle — from concept discovery to AI integration, multi-platform backend architecture, design systems, automated testing, GEO/AEO optimization, and production deployment.
Trigger Conditions
- Starting any new application development from scratch.
- Asking for a complete, end-to-end fullstack development roadmap.
- Orchestrating multiple domain skills across UI, Backend, AI/LLM, Database, Security, and Cloud.
Core Principles & Hard Gates
- Never Skip Phases: Each phase must be completed and validated before advancing to the next.
- Continuous Auto-Documentation: Invoke
auto-doc-updaterto log changes inCHANGELOG.mdandBLUEPRINT.mdafter every major milestone. - Strict Progress Tracking: Maintain a
PROGRESS.mdchecklist in the repository root. - State Preservation & Context: Utilize
session-handoff-resumewhen pausing work, andsession-context-loaderon every new session to preserve full context. - Efficiency: Keep
token-saveractive during large refactors to maintain a lean, powerful execution loop.
The 8-Phase Master Fullstack Pipeline
PHASE 1 PHASE 2 PHASE 3 PHASE 4
Discovery/PRD ---> Foundation ---> Database/ORM ---> Backend/APIs
| |
v v
PHASE 8 PHASE 7 PHASE 6 PHASE 5
Launch/Deploy <--- Security/GEO <--- Testing/QA <--- Frontend/UI
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.
- 6d ago Changed 54f27e86e1b5
- 7d ago First seen · 232 lines · 55 tokens per session scan A 5bfe591885cf
zero-to-prod-orchestrator is a skill published in the GitHub repository roedyrustam/vibes-plug (50 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 6,046 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-09-03.
Other skills, from other repositories
implement-improvements
Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
create-issue
Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue", "open an issue", "submit an issue", "report a bug", "file a bug report", "file a feature request", or "file a design proposal".
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
produck-feedback
Use when acting on real user feedback — you have a Produck feedback ticket or URL, or the user wants to fix something users complained about or build a feature users asked for. Pulls full feedback context through the Produck MCP and drives a feedback → aligned PRD → build loop. Triggers on "fix what users reported", a…
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".