agentsclimarketplace

Mission control security review

Skill MN755/Codex-Mission_Control/.codex/skills/mission-control-security-review

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-security-review

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

Ask Mission Control for a security review. Use when the user wants secrets risk, auth risk, dependency risk, command safety, file permission risk, deployment exposure, risky code patterns, or remediation planning summarized through Mission Control.

SKILL.md

2.1 KB, as published. Nobody here has run it

Mission Control Security Review

Purpose

Request or summarize a Mission Control security review without exposing secrets.

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 for a security review.
  • A release or handoff should include security posture.
  • A risky codebase needs threat-focused triage.

Workflow

  1. Request a security review through Mission Control.
  2. Read status, diagnostics, and risk resources.
  3. Summarize the findings across secrets, auth, dependencies, permissions, deployment exposure, and risky patterns.
  4. Return remediation steps and any user decisions needed.

Mission Control calls

Tools:

  • mission_control_start_task
  • mission_control_get_status

Resources:

  • mission-control://projects/{project_id}/risk-register
  • mission-control://projects/{project_id}/diagnostics
  • mission-control://projects/{project_id}/status

User-facing output

  • Cover secrets risk, auth or session issues, dependency risk, command safety, file permission risk, deployment exposure, risky code patterns, and remediation plan.
  • Keep secrets redacted and findings bridge-safe.

Approval behavior

If remediation implies destructive changes, deployment toggles, or tool-policy changes, present them as approvals rather than applying them silently.

Never do

  • Do not paste secrets or vulnerable payloads into chat.
  • Do not claim a clean bill of health without evidence.
  • Do not replace a real review with vague reassurance.

Failure and fallback

If dedicated security review tooling is not exposed yet, route the request through Manager-led task execution and summarize backed findings from risk and diagnostics resources.

Example invocation

Ask Mission Control for a security review of 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.