Mission control knowledge base map
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.
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-knowledge-base-mapAssembled 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
Build or inspect a graph-style map of docs, wiki pages, claims, entities, and relationships through Mission Control.
SKILL.md
1.7 KB, 317 tokens by cl100k_base, as published. Nobody here has run it
Mission Control Knowledge Base Map
Purpose
Turn documentation and wiki material into a navigable claim/entity map with source-aware summaries.
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 wants to understand a docs folder or knowledge base.
- Wiki pages need relationship mapping.
- Claims and entities need source tracking.
Workflow
- Ask Mission Control to scan docs and identify pages, entities, claims, links, and categories.
- Map explicit links separately from inferred relationships.
- Detect orphan pages, duplicate concepts, and stale claims.
- Return a source-aware map and recommended cleanup.
Mission Control calls
Tools:
mission_control_start_taskmission_control_get_status
Resources:
mission-control://projects/{project_id}/codebase-mapmission-control://projects/{project_id}/risk-registermission-control://projects/{project_id}/handoff
User-facing output
- Include entities, claims, relationships, orphan/stale areas, and source confidence.
Approval behavior
Ask before rewriting docs or committing generated graph artifacts.
Never do
- Do not blur explicit links with inferred relationships.
- Do not quote large copyrighted docs into chat.
- Do not claim knowledge-base completeness without scan coverage.
Failure and fallback
If docs are too large, propose an incremental scan scope.
Example invocation
Use Mission Control to map the docs folder into claims, entities, and stale areas.
Gives 0 of the 12 instructions most memory context skills give in 317 tokens
Counted across 674 of the 847 authors here whose files we hold, read 2026-08-06
- inform the user when setup is completein 21 of 674, across 6 files
- confirm the draft with the user before writingin 21 of 674, across 6 files
- update the agent skills block in place if it existsin 21 of 674, across 6 files
- present findings to the userin 20 of 674, across 5 files
- write the three docs files from seed templatesin 20 of 674, across 5 files
- ask the user about each decision one at a timein 19 of 674, across 4 files
- edit CLAUDE.md if it existsin 18 of 674, across 3 files
- explore current repo statein 18 of 674, across 3 files
- do not overwrite user edits to surrounding sectionsin 18 of 674, across 3 files
- back up the original file before overwritingin 16 of 674, across 8 files
- keep the memory index under 200 linesin 15 of 674
- Provide actionable steps and verificationin 13 of 674, across 2 files
Said here and by no other author read
- Identify pages, entities, claims, links, and categories
- Map explicit links separately from inferred relationships
- Detect orphan pages, duplicate concepts, and stale claims
- Return a source-aware map and recommended cleanup
- Include entities, claims, relationships, and source confidence
- Ask before rewriting docs or committing artifacts
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.