agentsclimarketplace

Mission control agent graph workflows

Skill MN755/Codex-Mission_Control/apps/mcp-server/src/mission_control_mcp_server/_bundled/skills/mission-control-agent-graph-workflows

An Open Source Platform For Building Projects With OpenAI's Codex, Claude CLI, And Other Coding LLMs Using Multi-Agent Swarms And Customizable Workflows. Runs On Windows, MacOS, And Linux.

Install
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-agent-graph-workflows

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing 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.

What its author says it does

Copied from the file, not written here

Design graph-style agent workflows with nodes, edges, gates, retries, checkpoints, and human approvals through Mission Control.

SKILL.md

1.8 KB, 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

  1. Ask Mission Control to define workflow nodes, edges, inputs, outputs, and gates.
  2. Identify deterministic steps, model steps, tool steps, human approvals, and checkpoints.
  3. Define retry and fallback behavior for each failure class.
  4. Summarize the graph and execute only through Mission Control approvals.

Mission Control calls

Tools:

  • mission_control_start_task
  • mission_control_get_status

Resources:

  • mission-control://projects/{project_id}/swarm-plan
  • mission-control://projects/{project_id}/agent-contracts
  • mission-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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.