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.10108 |
| Opus 5.5 | $0.00022 | $0.04043 |
| Sonnet 5.5 | $0.00011 | $0.02022 |
| Haiku 4.5 | $0.00006 | $0.01011 |
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 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 — 347 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 session-memory-manager 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
prd-architectto log changes inCHANGELOG.mdandBLUEPRINT.mdafter every major milestone. - Strict Progress Tracking: Maintain a
PROGRESS.mdchecklist in the repository root. - State Preservation & Context: Utilize
session-memory-managerwhen pausing work or starting a new session to preserve full context. - Sovereign Anti-Slop Mandate: Zero-tolerance for placeholders (
// TODO,// ...), mock data in prod, syntax comments, and sycophancy across all phases. Runnode scripts/check-anti-slop.js --strictas a mandatory validation gate before phase completion.
🐝 Swarm Execution Topologies & Subagent Delegation Protocols (2026 Master)
Whenever executing complex multi-domain phases, the Orchestrator MUST act as Swarm Director and delegate to specialized subagents in parallel:
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 Changed · -1 lines 3ff910162131
- 5d ago Changed · +1 lines adcf630562d8
- 6d ago Changed a377a390788f
- 8d ago Changed d920fcf00582
- 9d ago Changed · +14 lines e3c1fa8e7b8f
- 17d ago Changed 26707c5a62e0
- 22d ago Changed · +44 lines a8813700b484
- 23d ago Changed c09754a1b7ba
- 25d ago Changed 0013c7a41c9b
- 26d ago First seen · 289 lines · 55 tokens per session scan A 4ef40b3d9058
zero-to-prod-orchestrator is a skill published in the GitHub repository roedyrustam/vibes-plug (113 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 10,108 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
wayfinder
A planning method that maps a large, uncertain project into linked decision tickets in a repository's issue tracker. An issue tracker is a system for recording and organizing project work.
triage
A process for reviewing issues and outside pull requests through category and status labels. An issue is a recorded problem or request, while a pull request is a proposed code change for review.
to-tickets
A method for turning a plan, specification, or conversation into small tickets, where each ticket is a complete vertical slice of work and lists the tickets that must come first.
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
implement-spec
A coding workflow that implements a written specification through a set of linked tickets. It creates a branch and draft pull request, assigns independent work to separate agents, combines their changes, and prepares the result for review.
triage
A structured issue-triage process that moves issues and, where configured, pull requests through classification and status steps. Triage means deciding what a report is, whether more information is needed, and who should handle it.