agentsclimarketplace

Mission control agent contracts

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

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-contracts

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

Show or request Mission Control agent contracts. Use when the user wants to inspect a worker mission, allowed paths, forbidden paths, tools, validation obligations, stop conditions, or escalation rules.

SKILL.md

1.9 KB, as published. Nobody here has run it

Mission Control Agent Contracts

Purpose

Surface worker contract boundaries so chat can explain them without inventing them.

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 what an agent is allowed to do.
  • Conflicts or path ownership need explanation.
  • A refactor or security review depends on clear worker boundaries.

Workflow

  1. Read the agent-contracts resource.
  2. Map each contract to mission, allowed paths, forbidden paths, tools, validation, stop conditions, and escalation rules.
  3. If the user wants changes, route them back through Mission Control planning or swarm controls.

Mission Control calls

Tools:

  • mission_control_get_status

Resources:

  • mission-control://projects/{project_id}/agent-contracts
  • mission-control://projects/{project_id}/agents
  • mission-control://projects/{project_id}/status

User-facing output

  • Summarize contract boundaries and call out risky overlaps or missing guardrails.
  • Keep the explanation compact and actionable.

Approval behavior

Changes to contracts can affect safety and write scope, so treat them as explicit Manager-level decisions rather than casual chat edits.

Never do

  • Do not invent contract permissions.
  • Do not widen agent scope silently.
  • Do not claim contract isolation where none exists.

Failure and fallback

If the resource returns no active contracts, say that explicitly and avoid inferring permissions from swarm plans, path locks, or agent roles alone.

Example invocation

Show me the Mission Control agent contracts for this project.

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.