Mission control handoff audit burst

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

Use when Mission Control should recommend a read-only handoff audit burst for run instructions, validation evidence, limitations, docs quality, and security caveats.From its SKILL.md

Install

npx -y skills add MN755/Codex-Mission_Control --skill mission-control-handoff-audit-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.

SKILL.md

1.9 KB, 376 tokens by cl100k_base, as published. Nobody here has run it

Mission Control Handoff Audit Burst

Purpose

Use Mission Control to audit handoff quality with bounded read-only Codex subagents.

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 handoff exists but confidence is not high enough.
The user wants structured handoff review before trusting it.
Validation and docs need an independent audit pass.

Workflow

Read the latest handoff summary and validation posture.
Ask Mission Control for a handoff_audit burst recommendation.
Surface any approval decision in Codex chat.
If approved, show the planned auditors and expected outputs.
Ingest results so the Manager can tighten the handoff.

Mission Control calls

Daemon/API:

POST /api/projects/{project_id}/subagent-bursts/recommend
GET /api/subagents/batches/{batch_id}
POST /api/subagents/batches/{batch_id}/results

Resources:

mission-control://projects/{project_id}/handoff
mission-control://projects/{project_id}/validation-summary

User-facing output

Show what the audit burst is checking and why.
Keep the output concise, with clear evidence and caveats.

Approval behavior

Do not auto-approve a larger handoff audit burst.

Never do

Do not claim the handoff is trustworthy before the audit says so.
Do not run commands or edit docs by default.
Do not bypass Mission Control approval flow.

Failure and fallback

If burst planning is unavailable, fall back to the normal handoff summary and highlight evidence gaps manually.

Example invocation

Ask Mission Control whether we should run a handoff audit burst before accepting this handoff.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.