A dispatcher for a Vibe development loop, using repository state and a plan to choose the next prompt or action.

Use it to inspect loop status, select the next step, choose a named workflow, or run stricter checks for continuous development work.

It gives the agent a repeatable next step and can check workflow rules, instead of relying on an informal sense of what to do next.

How brifl/coding-agent-orchestration configures Codex

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/brifl/coding-agent-orchestration/main/.codex/skills/vibe-loop/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/brifl/coding-agent-orchestration

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/brifl/coding-agent-orchestration/vibe-loop/github.svg)](https://agentmods.dev/skills/brifl/coding-agent-orchestration/vibe-loop)

Your own site

<a href="https://agentmods.dev/skills/brifl/coding-agent-orchestration/vibe-loop"><img src="https://agentmods.dev/badge/skills/brifl/coding-agent-orchestration/vibe-loop/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/brifl/coding-agent-orchestration/vibe-loop"><img src="https://agentmods.dev/badge/skills/brifl/coding-agent-orchestration/vibe-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 772 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00018	$0.00772
Opus 5.5	$0.00007	$0.00309
Sonnet 5.5	$0.00004	$0.00154
Haiku 4.5	$0.00002	$0.00077

Measured 15d ago against content hash 7aec31469a4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vibe-loop 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.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/vibe_mark_done.py, scripts/vibe_next_and_print.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.codex/skills/vibe-loop/SKILL.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

Drive the Vibe workflow deterministically for a target repository.

This skill uses .vibe/STATE.md and .vibe/PLAN.md to recommend the next loop prompt and to validate invariants.

Inputs

Repo root path (default: current working directory)
Optional: --strict validation for CI-grade checks
Optional explicit legacy/custom runtime: --runtime-tools-dir <dir>

Runtime helpers

Source repo: tools/agentctl.py is the editable dispatcher source.
Installed skill: scripts/agentctl.py is generated from tools/agentctl.py by bootstrap tooling.
Skill-owned wrapper: scripts/vibe_next_and_print.py.

How to use

Show current status:
- Source repo: python3 tools/agentctl.py --repo-root . --format json status
- Installed skill directory: python3 scripts/agentctl.py --repo-root . --format json status
Recommend next loop:
- Source repo: python3 tools/agentctl.py --repo-root . --format json next
- Installed skill directory: python3 scripts/agentctl.py --repo-root . --format json next
Recommend next loop using a named workflow (for example workflows/continuous-refactor.yaml):
- Source repo: python3 tools/agentctl.py --repo-root . --format json next --workflow continuous-refactor
- Installed skill directory: python3 scripts/agentctl.py --repo-root . --format json next --workflow continuous-refactor
- Pass the workflow file stem (continuous-refactor), not the .yaml filename.
Validate invariants:
- Source repo: python3 tools/agentctl.py --repo-root . --format json validate
- Installed skill directory: python3 scripts/agentctl.py --repo-root . --format json validate
- Strict mode (recommended in CI): add --strict
Record loop completion from emitted LOOP_RESULT:
- Source repo: python3 tools/agentctl.py --repo-root . --format json loop-result --line 'LOOP_RESULT: {...}'
- Installed skill directory: python3 scripts/agentctl.py --repo-root . --format json loop-result --line 'LOOP_RESULT: {...}'
Print the next loop prompt body directly:
- Run: python3 scripts/vibe_next_and_print.py --repo-root . --show-decision
- The helper uses the managed bundle containing the wrapper and fails with reinstall guidance if that bundle is incomplete.
- --runtime-tools-dir is an explicit override; decision provenance labels it runtime_mode: explicit.

Read the full file on GitHub · 59 lines

Files

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.

Changes

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 · +2 lines 7aec31469a4d
2mo ago First seen · 57 lines · 18 tokens per session scan A 49530e77701d

Subscribe to this mod's changes

vibe-loop is a skill published in the GitHub repository brifl/coding-agent-orchestration (22 stars, last pushed 15d ago), licensed MIT. It adds 18 tokens to every session and 772 once invoked, about $0.0001 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.

Building agents

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

coding-agent-orchestration: Skill for Codex