agentsclimarketplace

Mission control handoff audit burst

Skill MN755/Codex-Mission_Control/plugins/mission-control/skills/mission-control-handoff-audit-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-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.

What its author says it does

Copied from the file, not written here

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

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

  1. Read the latest handoff summary and validation posture.
  2. Ask Mission Control for a handoff_audit burst recommendation.
  3. Surface any approval decision in Codex chat.
  4. If approved, show the planned auditors and expected outputs.
  5. 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.

Gives 0 of the 12 instructions most audit compliance skills give in 376 tokens

Counted across 937 of the 1,487 authors here whose files we hold, read 2026-08-07

  • Fetch latest guidelines before each reviewin 43 of 937, across 3 files
  • group findings by severityin 43 of 937
  • Check files against all fetched rulesin 42 of 937, across 2 files
  • Output findings in terse file:line formatin 41 of 937, across 3 files
  • Ask user which files to review if none specifiedin 41 of 937, across 3 files
  • Read specified files or prompt user for filesin 39 of 937, across 1 file
  • generate the audit reportin 33 of 937, across 30 files
  • assign a severity to every findingin 25 of 937
  • run automated accessibility scansin 23 of 937, across 13 files
  • output a markdown audit reportin 22 of 937
  • map findings to WCAG criteriain 20 of 937, across 10 files
  • confirm audit scopein 19 of 937, across 9 files

Said here and by no other author read

  • Read the latest handoff summary and validation posture
  • Ask Mission Control for a handoff audit burst recommendation
  • Surface any approval decision in chat
  • Show planned auditors and expected outputs if approved
  • Ingest results so the Manager can tighten the handoff
  • Keep the output concise with clear evidence and caveats

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

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.