suede-codex-fleet

Solid

Claude-directed parallel OpenAI Codex CLI worker fleet for bulk generation. Use when a job is high-volume, well-specified, and splits into independent worker-sized tasks (content batches, test generation, bulk refactors) and Codex CLI is installed and logged in. Claude decomposes, briefs, spawns codex exec runs in parallel, and review-gates every output. Workers are always codex exec processes billed to the user's OpenAI subscription — never substitute Claude subagent fan-out on any model, and halt rather than fall back if Codex CLI is unavailable. NOT FOR: multi-lane Claude agents coordinating one complex change (use suede-agent-teams); low-volume, judgment-dense copy Claude should write itself (use suede-copy or johnny-suede-write).

AI & Automation 135 stars 10 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
71
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Suede Fable Fleet The Suede Fable Fleet: a high-end Claude model is the admiral — it decomposes, briefs, and reviews — and parallel OpenAI Codex CLI workers are the fleet. Do not rename the folder or frontmatter `name` to match the brand. ## The workers are Codex processes — never Claude models **This is the economic point of the skill.** Codex workers bill to the user's OpenAI/ChatGPT subscription. Claude subagents bill to their Anthropic limit. Someone asking for a codex fleet is deliberately routing volume *off* the Anthropic meter — satisfying that request with Claude models inverts the cost model and spends the exact budget they were protecting. `codex exec` is therefore the only way a worker runs here. Never substitute `Agent`, `Task`, `Workflow`, subagent fan-out, or any other in-house orchestration for a worker — not with `fable`, not with `opus`, not with any model, not "just for this one batch". Claude's role is admiral only: decompose, brief, review, assemble. If you are about to spawn something that is not a `codex exec` process, you have left this skill — stop and re-read the routing table below. **Preflight failure is a halt, not a fallback.** If Codex CLI is missing, not logged in, or not on `PATH`, say which check failed and ask whether to proceed on Claude models, with a rough estimate of what that fan-out will consume. Never fall back silently. **What getting this wrong costs** (measured, 2026-07-27): a Claude-model fleet ran in place of an explicitl...

Details

Author
JasonColapietro
Repository
JasonColapietro/suede-creator-skills
Created
3 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

codex-director

A way of working where Codex is the default executor and Claude only directs. Load this skill for any task that involves reading code to understand current behavior, finding the root cause of a bug, implementing a change from requirements, reviewing a diff, or getting a second opinion, and whenever the user says "ask codex", "let codex look", or "use codex". Follow the process to dispatch work to codex-worker; Claude only writes the brief, judges the result, and makes the calls.

1 Updated yesterday
y-cruce
AI & Automation Listed

agent-fleet

Act as an orchestrator that plans work, delegates each piece to the right model across Claude Code and Codex (Opus, Sol, Sonnet, Terra, Luna, Haiku, Mini, Spark), reviews what comes back, and escalates on failure. Use when the user wants work split across models or backends, wants a cheaper/faster model to do the grunt work, wants a second model to review, or says things like "delegate this", "fan this out", "use the fleet", "have Codex do X", "have Claude do X", "route this to the right model", or "orchestrate this".

1 Updated 3 days ago
hopit-ai
AI & Automation Listed

codex

Run OpenAI Codex (the `codex` CLI, GPT models) as a managed subagent from Claude Code — start work in the background and get a run handle back immediately, watch its live event log at a controlled level of detail, interrupt and redirect a run, resume any earlier Codex thread including ones started in the Codex TUI, and collect results as text or schema-validated JSON. Use whenever work is being handed to Codex or GPT, when a second independent model should look at something, when an external agent should keep working while Claude does something else, or when an earlier Codex session needs continuing. Also covers Codex CLI setup, auth, sandbox and config diagnosis. Triggers include: codex, 코덱스, 코덱스로, 코덱스한테, ���덱스에게, GPT, GPT한테, GPT에게 시켜, delegate to codex, run with codex, ask GPT, resume codex. Not for Claude's own subagents, the Task tool, or background Bash — those are Claude doing the work itself. Not for Codex Cloud or `codex mcp-server` / `app-server`.

0 Updated 3 days ago
tjdwls101010