Borrowing it
Nothing to install: this file belongs to brifl/coding-agent-orchestration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/brifl/coding-agent-orchestration/main/.codex/skills/vibe-run/SKILL.mdgit clone --depth 1 https://github.com/brifl/coding-agent-orchestrationWrote 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/brifl/coding-agent-orchestration/vibe-run)<a href="https://agentmods.dev/skills/brifl/coding-agent-orchestration/vibe-run"><img src="https://agentmods.dev/badge/skills/brifl/coding-agent-orchestration/vibe-run/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/brifl/coding-agent-orchestration/vibe-run"><img src="https://agentmods.dev/badge/skills/brifl/coding-agent-orchestration/vibe-run.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.00058 | $0.01124 |
| Opus 5.5 | $0.00023 | $0.00450 |
| Sonnet 5.5 | $0.00012 | $0.00225 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
vibe-run 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 15d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe Run
Run the Vibe workflow as an agent loop. Treat .vibe/PLAN.md as a durable
execution backlog, not as a substitute for inspecting the repository.
Operating posture
$vibe-run is high-throughput scaffolding for complex work. It should keep Codex
moving through design, implementation, review, and handoff without letting process
become the product.
- Use evidence as lightweight trust-but-verify receipts, not comprehensive proof.
- Prefer one or two high-signal checks over broad verification when risk is low.
- Let non-building loops earn their cost: they should reduce rework, backsliding, rediscovery, or shaky handoffs.
- Keep moving when the next capability is safe; record useful non-blocking checks as concise backlog items instead of making them gate every loop.
- If an issue, checkpoint, or stage is blocked but later independent work can
safely proceed, mark it
[DEFERRED], add a short reason plus unblock/revisit condition, and move on. Waiting on human feedback is a valid deferral reason. - Revisit
[DEFERRED]items during design and consolidation; reactivate them when the unblock condition is true, otherwise keep the note compact.
Start
-
Read
AGENTS.md,.vibe/STATE.md, and.vibe/PLAN.mdin that order. -
From the repository root, dispatch with the explicit
vibe-runworkflow:python3 .codex/skills/vibe-loop/scripts/agentctl.py --repo-root . --format json next --workflow vibe-runIn this orchestration source repo, use
python3 tools/agentctl.py ...instead; the.codexdispatcher script is generated during install. -
Fetch
recommended_prompt_idfrom the returnedprompt_catalog_path:python3 .codex/skills/vibe-prompts/scripts/prompt_catalog.py <prompt_catalog_path> get <recommended_prompt_id>In this orchestration source repo, use
python3 tools/prompt_catalog.py ...instead. -
Follow the fetched prompt as the current loop. Inspect and edit the repository yourself;
scripts/vibe_run.pyis a terminal/headless helper, not a replacement for Codex executing the work. -
Emit and record the prompt's
LOOP_RESULT, then dispatch again.
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.
- 15d ago Changed · +5 lines 60fd114f40b2
- 2mo ago First seen · 101 lines · 58 tokens per session scan A fccdc7a5cd86
vibe-run is a skill published in the GitHub repository brifl/coding-agent-orchestration (22 stars, last pushed 15d ago), licensed MIT. It adds 58 tokens to every session and 1,124 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-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.