Mission control codebase knowledge graph

Skill MN755/Codex-Mission_Control/apps/mcp-server/src/mission_control_mcp_server/_bundled/skills/mission-control-codebase-knowledge-graph

Build or inspect a Mission Control codebase knowledge graph. Use for file/function/class maps, dependency relationships, architectural layers, guided tours, and searchable understanding.From its SKILL.md

Install

npx -y skills add MN755/Codex-Mission_Control --skill mission-control-codebase-knowledge-graph

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

2.0 KB, 379 tokens by cl100k_base, as published. Nobody here has run it

Mission Control Codebase Knowledge Graph

Purpose

Turn codebase understanding into a structured graph-like map that Mission Control can use for planning, onboarding, impact analysis, and handoffs.

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 to understand a repo.
A large codebase needs mapping before changes.
Planning needs dependencies, layers, or guided tour output.

Workflow

Ask Mission Control to scan project files, languages, frameworks, entrypoints, and instructions.
Request graph nodes for files, modules, classes, functions, commands, and domains where available.
Request edges for imports, calls, ownership, tests, and runtime relationships.
Summarize layers, hotspots, unknowns, and a guided reading order.

Mission Control calls

Tools:

mission_control_import_existing_codebase
mission_control_get_status

Resources:

mission-control://projects/{project_id}/codebase-map
mission-control://projects/{project_id}/swarm-plan
mission-control://projects/{project_id}/status

User-facing output

Provide key nodes, relationships, layers, hotspots, and the next-best files to read.

Approval behavior

Ask before running expensive scans, indexing huge folders, or committing generated graph artifacts.

Never do

Do not generate a graph that is pretty but useless.
Do not include secrets or bulky generated files.
Do not pretend inferred relationships are proven.

Failure and fallback

If graph generation is unavailable, use the existing codebase map and clearly label it as a map rather than a full graph.

Example invocation

Use Mission Control to build a knowledge graph for this repo and show me the guided tour.

What ships with it

Read from the repository

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