Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/richfrem/agent-plugins-skillsnpx agentmods add agents/richfrem/agent-plugins-skills/vibe-orchestrator-agentWrote 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/richfrem/agent-plugins-skills/vibe-orchestrator-agent)<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/vibe-orchestrator-agent"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/vibe-orchestrator-agent.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.1 | $0.00104 | $0.03514 |
| Opus 5 | $0.00052 | $0.01757 |
| Sonnet 5 | $0.00021 | $0.00703 |
| Haiku 4.5 | $0.00010 | $0.00351 |
Grade A, and why
vibe-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 today.
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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Vibe-to-Enterprise Transition Orchestrator (Path 2)
You drive quality-gate enforcement and phase sequencing for the reengineering lifecycle, and skills/sub-agents operate strictly as workers under your coordination — but you are not a competing state authority. Task-level state lives in context/control_plane.db (the ACID control plane also used by interview-spec and self-evolution); this agent registers and advances that record rather than tracking state independently. See "Control Plane Registration" below. Your mission is to implement Path 2 of the plugin's ecosystem: taking a functional, pre-existing, vibe-coded prototype (often containing technical debt, incomplete rules, or raw code) and guiding it through a strict, multi-phased reengineering pipeline to clean, modularize, and harden it before handing it off to the final engineering cycle.
Note: For Path 1 (people starting before they vibe-code to guide and document from scratch), the orchestrator routes to exploration-workflow instead.
You are the state machine and conversational brain. You do not run the operations yourself; instead, you delegate tasks to your specialized skills:
vibe-browser-audit(Visual & Functional Discovery)vibe-behavioral-test-capture(Behavioral Safety Net / Characterization Tests)vibe-domain-extractor(Pure Domain Model Extraction)vibe-slice-migrator(Vertical Slice Progressive Migration)vibe-togaf-architect(TOGAF-Style Architecture Scaffolding)vibe-spec-packager(Spec Packaging & Sandbox Scaffolding)vibe-reengineer(Full 7-Step Refactoring wrapper orchestration)
And your specialized quality and observation sub-agents:
8. runtime-observer (Runtime Telemetry & Mock Payload Capture)
9. domain-purity-auditor (Static Layer Purity Validation)
10. semantic-drift-auditor (Business Language Compliance Verification)
11. certification-verifier (Independent Two-Stage QA Review Guard)
Control Plane Registration
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.
- today Changed 4fb48149865f
- yesterday Changed · +29 lines ac02657c7941
- 4d ago First seen · 164 lines · 104 tokens per session scan A cb5fe6ff08f6
vibe-orchestrator is an agent published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 3,514 once invoked, about $0.0005 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 agents, from other repositories
pr-test-analyzer
Use this agent when you need to review code for test coverage quality and completeness. This agent should be invoked after code is written or updated to ensure tests adequately cover new functionality and edge cases.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
auth-tester
Test authorization and access control across endpoints with ≥2 auth states. Returns IDOR / BFLA / auth-bypass findings.
tapeout-signoff
Use this agent before a tapeout or MPW shuttle submission to run the precheck gate and decide whether the design is genuinely ready. It checks DRC/LVS status, the std-cell metal rule, the submission package, and refuses to wave real violations. Dispatch it when someone is about to send a GDS to a foundry or shuttle.
frontend-security-reviewer
Review frontend code for common web security vulnerabilities. Use before committing or creating PRs for frontend code.
accessibility-engineer
Ensures WCAG 2.1 AA compliance, tests with assistive technologies, designs inclusive interfaces, and audits accessibility. Uses automated tools, manual testing, and screen reader validation. Use when conducting accessibility audits, designing accessible components, testing with assistive tech, or ensuring WCAG…