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 kks0488/vibe-codex --skill vc-routergit clone --depth 1 https://github.com/kks0488/vibe-codexWrote 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/kks0488/vibe-codex/vc-router)<a href="https://agentmods.dev/skills/kks0488/vibe-codex/vc-router"><img src="https://agentmods.dev/badge/skills/kks0488/vibe-codex/vc-router.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.00036 | $0.00274 |
| Opus 5 | $0.00018 | $0.00137 |
| Sonnet 5 | $0.00007 | $0.00055 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
vc-router 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 8d 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
VC Router
Route once, then work
Classify the request by outcome, scope, risk, and need for persistence. Select one primary path:
- Simple answer or one-step reversible change: handle directly without another VC skill.
- Multi-step implementation or repair with end-to-end verification: use
vc-phase-loop. - Durable or cross-process coordination: use
vc-agent-teamsfor the mailbox and use built-in Codex subagents for actual in-session delegated work.
Do not force every request through the phase loop. Do not chain skills when one workflow is enough.
Routing rules
- Respect the user's explicit skill choice when it fits the task.
- Prefer the narrowest workflow that can produce the requested evidence.
- Use safe defaults for reversible implementation details.
- Ask when a missing decision changes scope, authority, safety, or public impact.
- If no VC workflow adds value, continue directly and say so briefly.
Output
State the selected path in one sentence, then execute it. Avoid long routing analyses.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 32 lines · 36 tokens per session scan A 4d4ddec19478
vc-router is a skill published in the GitHub repository kks0488/vibe-codex (11 stars, last pushed 25d ago), licensed MIT. It adds 36 tokens to every session and 274 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
boss-advanced
Advanced Boss orchestration patterns — Agent Teams leadership, 6-section delegation template, Skill vs Agent conflict resolution, Guardian pattern, and AI-slop detection.
gstack-sprint
3-Phase Sprint workflow — design → execute → review with user interaction at decision points.
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.
briefing-vault
Initialize, manage, and search the per-project .briefing/ vault. Obsidian-compatible persistent knowledge base.
maintain-codex-wiki
Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows…
orchestrate-engineering
Coordinate complex engineering work across bounded subagents while protecting the main context, preventing edit conflicts, and measuring whether delegation was worthwhile. Use when the user asks to delegate, parallelize, orchestrate, use subagents, fan out a review, or handle a large task with independent workstreams…