codex-workflows
Run a dynamic-workflow script on a local Codex App Server — orchestrate many Codex / GPT agents (the agent / parallel / pipeline / phase /…
Sorting a stream of records into a picture
What it does
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.
What it can touch
Includes 67 scripts
Your AI can run these when the skill is used — on your computer in a coding tool (which asks first unless you have told it not to), or in the AI’s own sandbox in Claude and ChatGPT.
How we know
Found in the skill’s folder: bin/codex-workflows.js, examples/agent-foreman.workflow.js, examples/benchmarks/warm-vs-cold.workflow.js, examples/bug-hunt.workflow.js….
Uses terminal commands
It shows your AI commands to run. In a coding agent that means your terminal; in a chat app it usually can’t.
How we know
The SKILL.md contains shell code blocks.
Its code sends data over the internet
A script in it uploads or posts data. That is normal for a skill that talks to a service — check that the address is the service you expect.
How we know
runner/bin/view-run.js line 1127: “fetch('/answer',{method:'POST',headers:{'content-type':'application/json'},body:JSON.stringify({id:q.id,answer:ans})})”. Read 2026-10-05, commit 16524be.
runner/bin/view-run.js, line 1127 ↗1 smaller thing worth knowing
Contains commands that delete or overwrite. Usually legitimate — listed so nothing is hidden.
How we know
Contains commands that delete or overwrite — runner/test/codex-session.test.js line 327. Read 2026-10-05, commit 16524be.
runner/test/codex-session.test.js, line 327 ↗No serious risk pattern found
Launch7’s automated check read all 90 text files in this skill and matched none of its serious risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit 16524be by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to scasella/claude-dynamic-workflows-codex: 2026-07-11 (86 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Partly. Upload it in Claude’s settings — the instructions work; the scripts need the full folder.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
This skill ships 67 scripts beside its instructions. The download here is the SKILL.md alone — enough for the instructions, not for the parts that run code. Use the command route, or take the full folder from the repository.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end