What is mission-control CLAUDE.md?

Repository instructions for Mission Control, an open-source web dashboard for coordinating AI agents, tasks, workflows, and costs. They describe setup, prerequisites, running methods, Docker, and checks.

Use them to install dependencies, build or run the dashboard, configure its first administrator, use Docker, and run tests, type checks, and linting.

They give a coding agent the required environment and commands, reducing setup mistakes and inconsistent development workflows.

mission-control CLAUDE.md — Instructions file for Claude Code by builderz-labs: Repository instructions for Mission Control, an open-source

About the project

Mission Control is a self-hosted dashboard for managing AI-agent work, including task dispatch, run review, spending tracking, and coordination of different agent runtimes. Operators use it to oversee OpenClaw, Claude Code, Codex, and other runtimes from one local interface. The catalogue add-ons provide instructions and skills for working with Mission Control.

builderz-labs/mission-control · 6,174 stars · on GitHub · mc.builderz.dev

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add instructions/builderz-labs/mission-control/claude-md

Clone the repo

git clone --depth 1 https://github.com/builderz-labs/mission-control

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/builderz-labs/mission-control/claude-md.svg)](https://agentmods.dev/instructions/builderz-labs/mission-control/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/builderz-labs/mission-control/claude-md"><img src="https://agentmods.dev/badge/instructions/builderz-labs/mission-control/claude-md.svg" alt="Measured on agentmods" height="20"></a>

Per session 891 This file is loaded in full into every session.

When invoked 891 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00891	$0.00891
Opus 5	$0.00445	$0.00445
Sonnet 5	$0.00178	$0.00178
Haiku 4.5	$0.00089	$0.00089

Measured 6d ago against content hash 71f535b193d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

mission-control CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mission Control

Open-source dashboard for AI agent orchestration. Manage agent fleets, track tasks, monitor costs, and orchestrate workflows.

Stack: Next.js 16, React 19, TypeScript 5, SQLite (better-sqlite3), Tailwind CSS 4, Zustand, pnpm

Prerequisites

Node.js >= 22 (LTS recommended; 24.x also supported)
pnpm (corepack enable to auto-install)

Setup

pnpm install
pnpm build

Secrets (AUTH_SECRET, API_KEY) auto-generate on first run if not set. Visit http://localhost:3000/setup to create an admin account, or set AUTH_USER/AUTH_PASS in .env for headless/CI seeding.

Run

pnpm dev              # development (localhost:3000)
pnpm start            # production
node .next/standalone/server.js   # standalone mode (after build)

Docker

docker compose up                 # zero-config
bash install.sh --docker          # full guided setup

Production hardening: docker compose -f docker-compose.yml -f docker-compose.hardened.yml up -d

Tests

pnpm test             # unit tests (vitest)
pnpm test:e2e         # end-to-end (playwright)
pnpm typecheck        # tsc --noEmit
pnpm lint             # eslint
pnpm test:all         # lint + typecheck + test + build + e2e

Key Directories

src/app/          Next.js pages + API routes (App Router)
src/components/   UI panels and shared components
src/lib/          Core logic, database, utilities
.data/            SQLite database + runtime state (gitignored)
scripts/          Install, deploy, diagnostics scripts
docs/             Documentation and guides

Path alias: @/* maps to ./src/*

Data Directory

Set MISSION_CONTROL_DATA_DIR env var to change the data location (defaults to .data/). Database path: defaults to <MISSION_CONTROL_DATA_DIR>/mission-control.db.

Conventions

Commits: Conventional Commits (feat:, fix:, docs:, test:, refactor:, chore:)
No AI attribution: Never add Co-Authored-By or similar trailers to commits
Package manager: pnpm only (no npm/yarn)
Icons: No icon libraries -- use raw text/emoji in components
Standalone output: next.config.js sets output: 'standalone'

Read the full file on GitHub · 106 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 106 lines · 891 tokens per session scan A 71f535b193d8

Subscribe to this mod's changes

mission-control CLAUDE.md is an instructions file published in the GitHub repository builderz-labs/mission-control (6,174 stars, last pushed yesterday), licensed MIT. It adds 891 tokens to every session, about $0.0045 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Building agents Project management agent-orchestration ai-agents developer-tools nextjs openclaw sqlite

mission-control CLAUDE.md

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Mission Control

Prerequisites

Setup

Run

Docker

Tests

Key Directories

Data Directory

Conventions

What this file has done since we first saw it

Other instructions, from other repositories

Paddock AGENTS.md

Paddock CLAUDE.md

souls-directory CLAUDE.md

souls-directory AGENTS.md

palaia AGENTS.md

claw-orchestrator CLAUDE.md