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/chentao326/vibe-code/codex-self-handoffnpx skills add chentao326/vibe-code --skill codex-self-handoffgit clone --depth 1 https://github.com/chentao326/vibe-codeWrote 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/chentao326/vibe-code/codex-self-handoff)<a href="https://agentmods.dev/skills/chentao326/vibe-code/codex-self-handoff"><img src="https://agentmods.dev/badge/skills/chentao326/vibe-code/codex-self-handoff.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.00113 | $0.01447 |
| Opus 5 | $0.00056 | $0.00724 |
| Sonnet 5 | $0.00023 | $0.00289 |
| Haiku 4.5 | $0.00011 | $0.00145 |
Grade A, and why
codex-self-handoff 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 3d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Self Handoff
Overview
Enable Codex to follow a disciplined 6-phase workflow entirely on its own. Codex switches between Architect mode (design, plan, review) and Builder mode (implement, fix). Signal files in handoff/ enforce phase discipline and prevent skipping steps.
Workflow
Spec ──→ Plan ──→ Build ──→ Review ──→ Polish ──→ Commit
Architect Architect Builder Architect Builder 任一
All roles are filled by Codex. The signal files enforce that you complete each phase before moving to the next.
Phase Detection
Always detect the current phase before acting:
python3 <skill_dir>/scripts/check_phase.py
| Signal File | Phase | Mode | Action |
|---|---|---|---|
| (none) | Init | Architect | Write spec to specs/<feature>.md, then write handoff/plan-ready.json |
plan-ready.json |
Plan Ready | — | Tell user plan is ready. Proceed only when user confirms. |
build-done.json |
Build Done | Architect | Review git diff against spec. Write review-notes.md + review-passed.json or review-fixes.json |
review-fixes.json |
Fixes Needed | Builder | Fix issues from review-notes.md, write polish-done.json |
polish-done.json |
Polish Done | Architect | Re-review fixes. Write review-passed.json or review-fixes.json |
review-passed.json |
Ready | Builder | Generate commit message and commit. Write committed.json |
committed.json |
Done | — | Announce completion. |
Full signal file schemas: references/protocol.md.
Mode Switching
You switch between two modes depending on the current phase:
Architect Mode
- Design specs and write acceptance criteria
- Decompose features into ordered tasks with dependencies
- Review code against specs
- Grade issues P0 (blocking) / P1 (should fix) / P2 (style)
- Do NOT write implementation code in this mode
Builder Mode
- Execute tasks from
plan-ready.jsonin dependency order - Fix issues from
review-notes.mdby priority - Write implementation code, tests, and documentation
- Do NOT redesign architecture or rewrite specs in this mode
What ships with it
4 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.
- 3d ago First seen · 149 lines · 113 tokens per session scan A 1231c2a73485
codex-self-handoff is a skill published in the GitHub repository chentao326/vibe-code (2 stars, last pushed 3mo ago), licensed MIT. It adds 113 tokens to every session and 1,447 once invoked, about $0.0006 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…