agentsclimarketplace

Mission control subagent burst

Skill MN755/Codex-Mission_Control/apps/mcp-server/src/mission_control_mcp_server/_bundled/skills/mission-control-subagent-burst

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-subagent-burst

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

Recommend or review Mission Control Codex subagent bursts for bounded read-heavy work. Use when the user wants parallel exploration, review, planning, handoff audit, or failure diagnosis without replacing the normal worker system.

SKILL.md

2.4 KB, as published. Nobody here has run it

Mission Control Subagent Burst

Purpose

Route short-lived Codex subagent burst recommendations through Mission Control.

The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager.

Use when

  • The task is read-heavy and parallelizable.
  • The user wants bounded parallel exploration or review.
  • Mission Control should recommend whether a burst is worth it.

Workflow

  1. Check status and current orchestration context.
  2. Fetch subagent policy.
  3. Ask Mission Control to recommend a burst for the current task.
  4. If a pending decision is created, render it in Codex chat and wait for the user.
  5. After approval, fetch the batch and present spawn instructions or manual prompt text.
  6. When results come back, send them to Mission Control result ingestion.

Mission Control calls

Tools:

  • mission_control_get_status

Daemon/API:

  • GET /api/subagent-policy
  • POST /api/projects/{project_id}/subagent-bursts/recommend
  • GET /api/projects/{project_id}/subagent-batches
  • GET /api/subagents/batches/{batch_id}
  • POST /api/subagents/batches/{batch_id}/results
  • GET /api/decisions/{decision_id}/bridge-message
  • POST /api/decisions/{decision_id}/answer

Resources:

  • mission-control://projects/{project_id}/status
  • mission-control://projects/{project_id}/pending-decisions

User-facing output

  • Explain whether Mission Control recommends a burst.
  • Show purpose, count, risk, intensity, and the proposed subagent list.
  • If approved, show spawn instructions and expected report format.

Approval behavior

Never bypass a subagent_burst_approval pending decision. Larger bursts must be answered by the user in Codex chat.

Never do

  • Do not replace the normal Mission Control worker system.
  • Do not default to file edits or commands.
  • Do not recursively fan out more agents.

Failure and fallback

If burst planning is unavailable, say so clearly and fall back to normal Mission Control planning or status-only guidance.

Example invocation

Ask Mission Control whether a read-only subagent burst makes sense for this repo review.

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.