What it does
Run Claude Code dynamic workflows on a local Codex (GPT) backend, plus an interactive run viewer
- Connects Instruction files the AI reads; connects to nothing
- Account or key No key needed
- Category Coding
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/scasella-claude-dynamic-workflows-codex)Use together with
MCP servers that connect the AI to services for the same work
Fallow
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Desktop Commander
MCP server for terminal commands, file operations, and process management
Similar Skills
Same kind of work, ordered like the Skills list
| This one claude-dynamic-workflows-codex | rea | graphify | MoneyPrinterTurbo | archify | |
|---|---|---|---|---|---|
| Maker | scasella | morluto | Graphify-Labs | harry0703 | tt-a1i |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 330 | 463,254 | 148,775 | 143,788 | 97,049 |
| Last code change | Jul 11, 2026 | Nov 16, 2026 | Nov 16, 2026 | Nov 13, 2026 | Nov 15, 2026 |
| License | MIT | MIT | Apache-2.0 | MIT | Apache-2.0 |
1 skills (instruction sets) by scasella that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCodex
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account scasella (person), 11 years old
- Use and upkeep
★ 330 stars, few users so far · code last changed Jul 11, 2026
- Any scripts?
67 scripts that can run on a computer: bin/codex-workflows.js, runner/bin/compare-runs.js, runner/bin/fleet.js, runner/bin/supervise.js and 63 more
- Uses the internet?
Could not check every script (some are too large); read them first
- Changes machine-wide settings?
Scripts that touch settings folders (~/.claude or settings.json): runner/src/agentTypes.js, scripts/sync-skill.js
Checked automatically from the repo files at commit 16524be (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (433). Use "Let the AI install it" instead
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /claude-dynamic-workflows-codex or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
The maker’s recommended way
Checking the commands · copy buttons appear once they pass
Copied from the maker’s README; it downloads and runs the maker’s code
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Claude Code, then type /claude-dynamic-workflows-codex or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the codex-workflows folder at ~/.agents/skills/codex-workflows
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick claude-dynamic-workflows-codex
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
In Cursor’s Agent chat, type / and pick claude-dynamic-workflows-codex
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: codex-workflows
description: >-
Run a dynamic-workflow script on a local Codex App Server — orchestrate many
Codex / GPT agents (the agent / parallel / pipeline / phase / budget DSL)
instead of Claude subagents, for codebase audits, large migrations, and
multi-agent review or research. Give it one or two rough sentences and it
compiles the right harness for you; add --multi for a supervised fleet of
concurrent workflows. Manual-invoke only via /codex-workflows.
disable-model-invocation: true
---
# Codex Workflows
Run a Claude Code dynamic-workflow script against a local **Codex App Server**.
The authoring surface is identical to native dynamic workflows — `export const
meta` plus a body using `agent()`, `parallel()`, `pipeline()`, `phase()`,
`log()`, `args`, `budget`, `workflow()` — but every `agent()` call runs as one
Codex (GPT) thread+turn instead of a Claude subagent.
**Manual-invoke only.** Claude does not auto-trigger this skill
(`disable-model-invocation: true`); it runs only when the user types
`/codex-workflows` or explicitly asks for a Codex workflow. Once invoked, follow
the loop below — the work runs on Codex/GPT agents. If the user actually wanted
Claude subagents, say so and point them at the native Workflow tool.
`RUNNER` below means the bundled runner directory: **`runner/` relative to this
skill's base directory** (shown when the skill loads). For a classic skills-dir
install that is `~/.claude/skills/codex-workflows/runner` — the literal paths in
the examples below assume it; substitute your base directory if this skill is
installed as a plugin. It is dependency-free Node ≥ 18.
## Default rough-intent mode
**One or two rough sentences is enough.** You do not need to hand this skill a
fully-engineered spec — describe what you want (e.g. `/codex-workflows Harden this
goal before I run it`) and the skill compiles it into an operational harness itself:
it classifies the job, picks the smallest workable scale, an archetype, and a
harness pattern, builds a task contract, composes phases, casts personas, applies
the quality/epistemic standards, authors the script, picks safe run settings, and
runs it — **stating its assumptions** as it goes.
Operating rules in this mode:
- The rough intent is the contract. Make reasonable assumptions for anything left
unspecified and **state them**; do not interrogate the user with follow-ups.
- Choose the **smallest useful harness**, not the largest possible one (see the
*Anti-overbuild rule*).
- **Do not emit a giant prompt for the user to paste back.** Compile and proceed to
authoring/running. (The one exception is `prompt-only` mode — see *Mode detection*.)
- This **replaces any external "metaprompt"**: the expansion now happens inside the
skill. The whole *Compiling rough intent into a workflow* section below is that
compiler.
## Default execution checklist
Every run, in order (the sections below expand each step):
1. **Preflight** Codex once (`handshake.js`); note the latest frontier model.
2. **Compile** the rough intent: classify the job → scale → archetype → pattern
(name the failure mode it prevents) → task contract. **State your assumptions.**
3. **Author** the script into the repo (`./<name>.workflow.js`).
4. **Settings:** `--frontier` · effort by scale (`--effort medium` for a
`quick_harness`, `--auto-effort` for `standard`/`deep`) · `--sandbox read-only`
unless it must write · a bounded `--budget` · strict schemas (`additionalProperties:false`).
5. **Size it** — run `--plan` first for any expensive or complex workflow.
6. **Run** on the Codex runner (never the native `Workflow` tool).
7. **Surface** — inline ASCII map + `summarize-run` highlights; cite the script,
journal, viewer, report, and run-summary paths (see *Output behavior*).
## Mode detection
Read the mode from the user's phrasing, then behave accordingly:
| Mode | Trigger | Behavior |
|------|---------|----------|
| **default** (rough-intent) | 1–2 rough sentences | Compile internally → author → run. State assumptions. |
| **`--multi`** (fleet) | the `--multi` flag, or "fleet" / "several workflows at once" | Compile a **fleet plan** (2–4 concurrent variant workflows, similar and/or diverse), launch them in the background, and **supervise**: poll `fleet status`, answer gates, steer, kill, fork, then synthesize. See *Fleet mode*. |
| **`prompt-only`** | "prompt-only", "just the invocation", "don't run it" | Emit a complete `/codex-workflows` invocation/spec (the A–L structure below) and **STOP** — do not author or run. |
| **`write-only`** | "write it but don't run", "author only" | Author the workflow script, print its path, stop before running. |
| **`run-existing`** | a script path or saved-workflow name is given | Skip compilation; run that script/name through the runner. |
| **`quick`** | "quick", "small", "cheap" | Bias to a `quick_harness` (2–5 agents). |
| **`deep`** | "deep", "thorough", "exhaustive" | Allow a larger / `deep_harness`; justify the size. |
| **`no-write`** | "don't write files", "just tell me" | Return final JSON/Markdown only; no report/source files; `--sandbox read-only`. |
Two precedence rules: if the user gives a **script path or saved name**, run it
(don't recompile). If the user gives a **detailed spec**, honor it as written but
still apply the safety + run defaults below. Otherwise it's rough intent → compile.
In **`prompt-only`**, the invocation you emit follows the same A–L structure the
skill builds internally: **A** name · **B** purpose · **C** task contract · **D**
inputs / context reconstruction · **E** phases · **F** personas · **G** anti-wrapper
standards · **H** outputs · **I** run settings · **J** safety / epistemics · **K**
final-response format · **L** productization. Then stop — do not run.
## The loop
In default rough-intent mode, do steps 1–2 **silently** and state your assumptions
before authoring. The mechanics below — handshake, the run command, the inline map —
are unchanged; steps 2 and 4 are where rough intent gets compiled.
1. **Preflight** — once per session, or whenever a run fails to connect, confirm
Codex is reachable and authed:
```bash
node ~/.claude/skills/codex-workflows/runner/test/handshake.js
```
It prints `state: ready` and the available models. If it fails, tell the user
to run `codex login` (the runner needs a logged-in `codex` CLI on PATH).
From that list, note the **latest frontier model** — the newest flagship
general model (not a `-mini`/`-spark` variant; `model/list` flags it
`isDefault` and its description calls it the strongest). The GPT-5.6 Codex
series is Sol (flagship), Terra (balanced), and Luna (efficient); today the
frontier is `gpt-5.6-sol`. Every agent in the run uses it (see *Model*).
2. **Compile** the rough intent into a workflow (see *Compiling rough intent into a
workflow*): classify the job → pick the scale → pick the archetype → pick the
pattern and name the failure mode it prevents → build the task contract → compose
the phases → cast the personas → apply the standards. **State the resulting
assumptions** to the user before authoring.
3. **Author** a workflow script from that compile (see *Authoring*). Write it into
the user's project so they can read and rerun it — `./<name>.workflow.js`, or
`workflows/<name>.workflow.js` / `examples/harness-zoo/<name>/` for a reusable
harness. Scripts are plain JavaScript using only the injected globals (no imports).
4. **Choose run settings** (see *Run defaults*): `--frontier`, the effort flag for
the chosen scale (`--auto-effort` for a standard/deep harness, `--effort medium`
for a quick one), a read-only sandbox unless the run must write, and a bounded
`--budget`. For an expensive or complex workflow, **`--plan` first** — a no-token
dry run that counts agents per phase/effort and estimates a `--budget`.
5. **Run** it — **always pass `--frontier`**, plus the effort flag for tDiscussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 330
- Maker
- scasella
- License
- MIT
- Last code change
- Jul 11, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- agent-orchestration, agent-skills, agents, claude-code, codex, dynamic-workflows, fleet-supervision, multi-agent, openai, orchestration, visualization, workflow