Mission control memory state policy

Skill MN755/Codex-Mission_Control/.codex/skills/mission-control-memory-state-policy

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-memory-state-policy

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

Define memory, state, checkpoints, resumability, and retention policy for Mission Control workflows and agents.

SKILL.md

1.8 KB, 333 tokens by cl100k_base, as published. Nobody here has run it

Mission Control Memory And State Policy

Purpose

Control what Mission Control remembers, where it stores state, and how agents resume without hallucinating continuity.

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 user asks how state, memory, checkpoints, or resumability work.
A workflow needs durable context or retention limits.
Privacy or cleanup rules matter.

Workflow

Ask Mission Control for current project state, runtime paths, and handoff artifacts.
Classify state as ephemeral, project-local, reusable, or sensitive.
Define retention, redaction, checkpoint, and resume rules.
Return policy and any cleanup or snapshot actions.

Mission Control calls

Tools:

mission_control_get_status
mission_control_request_snapshot

Resources:

mission-control://projects/{project_id}/decision-ledger
mission-control://projects/{project_id}/handoff
mission-control://projects/{project_id}/diagnostics

User-facing output

Explain stored state, retention, resume points, privacy risks, and cleanup options.

Approval behavior

Ask before deleting state, exporting memory, or persisting sensitive context.

Never do

Do not hide memory locations.
Do not retain secrets by default.
Do not resume from stale assumptions without checking status.

Failure and fallback

If state inventory is incomplete, recommend a snapshot and diagnostic pass.

Example invocation

Use Mission Control to explain what it remembers for this project and how to clean it up.