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/alanshurafa/co-evolution/codex-buildnpx skills add alanshurafa/co-evolution --skill codex-buildgit clone --depth 1 https://github.com/alanshurafa/co-evolutionWhat 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.00181 | $0.04599 |
| Opus 5 | $0.00090 | $0.02299 |
| Sonnet 5 | $0.00036 | $0.00920 |
| Haiku 4.5 | $0.00018 | $0.00460 |
Grade A, and why
codex-build 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 2d 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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/codex-build - Detached Codex Execution with Gate-Based Review
This is the orchestration protocol behind the "best Claude plans, Codex executes, best Claude reviews" model ladder. The session is the composer and the reviewer; Codex is the executor. The defining rule: the session is NEVER kept busy while Codex grinds. You kick the runner as a background task, end your turn, and the harness wakes you when it exits.
Use /dev-review instead when you want the classic interactive
compose-bounce-execute loop in one session (you watch every pass). Use
/co-evolution for questions, drafts, plans, and document refinement with no
code execution.
The protocol has five steps. Steps 1-3 happen in the FIRST turn (preflight, plan, kick-and-stop). Steps 4-5 happen on WAKE, after the background task exits.
Step 1: PREFLIGHT (one turn, before planning)
Run these checks. Each gate either passes, degrades with a stated fallback, or dies with a fix hint.
Codex present
command -v codex
If missing, die with the install hint:
codex CLI not found. On this Mac with Codex.app installed:
ln -s "/Applications/Codex.app/Contents/Resources/codex" ~/.local/bin/codex
Otherwise install the CLI:
npm i -g @openai/codex
Then re-run /codex-build.
Claude CLI auth probe (decides the verifier seat)
The runner's claude verifier seat runs in a headless shell that does NOT carry
the interactive app's session token. Probe it:
claude -p --output-format text --model claude-haiku-4-5-20251001 "ping" 2>&1 | head -2
- If the output contains
Not logged in(or/login): the runner's claude verifier seat cannot run. DEGRADE — kick with--verifier codexso the verify phase uses Codex's schema-bound review instead. Tell the user plainly: the in-session review gate (Step 4, which YOU run) is then the only Claude-side review of the diff, and to runclaude /loginin a terminal to restore the full ladder (the claude verifier seat inside the runner). - Otherwise: the full ladder is available. Kick with the preset's default claude
verifier (best/Opus, max effort) — no
--verifieroverride needed.
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.
- 2d ago First seen · 411 lines · 181 tokens per session scan A 4c144b59202c
codex-build is a skill published in the GitHub repository alanshurafa/co-evolution (3 stars, last pushed 3d ago), licensed MIT. It adds 181 tokens to every session and 4,599 once invoked, about $0.0009 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
recursive-task-optimizer
Build, configure, run, inspect, or troubleshoot agent-agnostic recursive improvement loops for a repository or artifact. Use when a task should be attempted repeatedly by Claude Code, Codex CLI, Hermes, or another CLI agent; when candidates must inherit mutable task instructions, a self-improving meta-procedure, and…
react-node-practices
// ❌ 错误：硬编码密钥 const apiKey = "sk-proj-xxxxx" const dbUrl = "postgres://user:pass@localhost/db".
design-audit
这是一个完整的 UI/UX 审计工作流，基于 Steve Jobs 和 Jony Ive 的设计哲学。用于对现有应用进行系统性审计，输出分阶段改进计划。.
technical-cofounder
Technical Co-Founder workflow for building a real, launchable product with strict phase gates (Discovery → Planning → Building → Polish → Handoff). Use when the user wants to build/ship an app/product/MVP for real usage or public launch.
manus-kickoff
版本: 1.0.0 作者: sumulige 标签: [workflow, planning, manuscript] 难度: 中级.
test-master
Skill "test-master" from sumulige/sumulige-claude, covering test master, 核心职责, 工作模式, 模式 1：tdd 开发 and 模式 2：e2e 测试.