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 agentmods add skills/kks0488/vibe-codex/vc-phase-loopnpx skills add kks0488/vibe-codex --skill vc-phase-loopgit 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-phase-loop)<a href="https://agentmods.dev/skills/kks0488/vibe-codex/vc-phase-loop"><img src="https://agentmods.dev/badge/skills/kks0488/vibe-codex/vc-phase-loop.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 | $0.00050 | $0.00554 |
| Opus 5 | $0.00025 | $0.00277 |
| Sonnet 5 | $0.00010 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
vc-phase-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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VC Phase Loop
Outcome
Complete the requested work within the user's scope and authority, then support the completion claim with executed checks and concrete evidence.
1. Scope and risk
- Read applicable repository instructions before editing.
- Separate requirements from assumptions.
- Identify destructive, costly, credential-sensitive, public, or externally consequential actions.
- Proceed with reversible in-scope choices. Ask when an unanswered choice materially changes the result or requires authority the user has not granted.
2. Choose task depth
- Small: execute directly, then verify.
- Multi-step: keep a short plan with one active step.
- Long-running or resumable: create
.vc/work-{timestamp}.mdwith requirements, decisions, status, blockers, and completion evidence. Update it at decision or phase boundaries, not after every command.
Do not inflate a task to reach a fixed phase count.
3. Execute
- Follow existing project patterns.
- Keep changes minimal and reviewable.
- Use built-in Codex subagents only for independent work that benefits from separate context, such as exploration, test execution, or review.
- Avoid parallel write-heavy work unless file ownership is clearly separated.
- Preserve user changes and stay within the approved roots.
4. Recover intelligently
Use the Two-Strike rule:
- Diagnose the first failure and try a targeted correction.
- If the same failure repeats, stop using the same approach.
- Re-check assumptions, inspect the root cause, and choose a materially different strategy.
- If progress requires missing authority, credentials, money, user input, or external state, report the blocker instead of pretending to continue.
Retries are bounded by new information. Never promise guaranteed success or an infinite loop.
5. Verify proportionally
Prefer the project's own checks in this order when available:
- focused tests for changed behavior;
- lint, type, or syntax checks;
- broader tests or build for higher-risk changes;
- a real user-path exercise when practical.
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.
- 4d ago First seen · 72 lines · 50 tokens per session scan A 55cb68a5c403
vc-phase-loop is a skill published in the GitHub repository kks0488/vibe-codex (11 stars, last pushed 21d ago), licensed MIT. It adds 50 tokens to every session and 554 once invoked, about $0.0003 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
loop
Use only when user explicitly invokes $loop.
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.
compact-kb
Use only when user explicitly invokes $compact-kb.