Mission control agent graph workflows
Design graph-style agent workflows with nodes, edges, gates, retries, checkpoints, and human approvals through Mission Control.From its SKILL.md
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-agent-graph-workflowsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- fetches URLsInstructs the agent to fetch 3 URLs, including mission-control://projects/{project_id}/swarm-plan and 2 more.
SKILL.md
1.8 KB, 338 tokens by cl100k_base, as published. Nobody here has run it
Mission Control Agent Graph Workflows
Purpose
Model complex agent work as controllable graph workflows instead of linear hope with extra steps.
The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager.
Use when
- A task needs branching, retries, approval gates, or subagents.
- The user wants a workflow diagram or execution plan.
- Failure handling and resumability matter.
Workflow
- Ask Mission Control to define workflow nodes, edges, inputs, outputs, and gates.
- Identify deterministic steps, model steps, tool steps, human approvals, and checkpoints.
- Define retry and fallback behavior for each failure class.
- Summarize the graph and execute only through Mission Control approvals.
Mission Control calls
Tools:
mission_control_start_taskmission_control_get_status
Resources:
mission-control://projects/{project_id}/swarm-planmission-control://projects/{project_id}/agent-contractsmission-control://projects/{project_id}/decision-ledger
User-facing output
- Provide nodes, edges, gates, retries, checkpoints, and current execution state.
Approval behavior
Ask before increasing agent count, adding tools, or executing risky branches.
Never do
- Do not spawn parallel work outside Mission Control.
- Do not hide approval gates.
- Do not let graph complexity outrun the task.
Failure and fallback
If graph execution is overkill, recommend a simpler linear workflow and say why.
Example invocation
Use Mission Control to design a graph workflow for release validation and rollback.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.