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.
npx agentmods add instructions/andy5090/central-mcp/agents-mdgit clone --depth 1 https://github.com/andy5090/central-mcpWhat 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 | $0.01742 | $0.01742 |
| Opus 5 | $0.00871 | $0.00871 |
| Sonnet 5 | $0.00348 | $0.00348 |
| Haiku 4.5 | $0.00174 | $0.00174 |
Grade C, and why
central-mcp AGENTS.md scanned grade C with 1 finding 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
5. `rm -rf dist && uv build`. Copies of this mod
1 near-identical copy found in the catalogue:
- central-mcp CLAUDE.md — 88% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
central-mcp — development guide
You are working on the central-mcp codebase itself. This file is for contributors (human or agent) editing the source tree. The runtime orchestrator instructions — the ones that describe how dispatch / check_dispatch should be used and what the observation layer does — live separately in src/central_mcp/data/{CLAUDE,AGENTS}.md and get copied to ~/.central-mcp/ on first launch. Don't confuse the two roles:
| File path | Role | Audience |
|---|---|---|
src/central_mcp/data/{CLAUDE,AGENTS}.md |
Runtime, shipped with the wheel | Orchestrator agent running inside a user's ~/.central-mcp/ session |
/{CLAUDE,AGENTS}.md (repo root) |
Dev-mode, NOT shipped | Anyone editing central-mcp's source |
What central-mcp is
A Python MCP server + CLI that acts as an orchestrator-agnostic dispatch hub across a user's registered projects. Each project is associated with a coding-agent CLI (claude / codex / gemini / droid / opencode). Dispatches are non-blocking subprocesses in the project's cwd; results stream to ~/.central-mcp/logs/<project>/dispatch.jsonl and can be tailed via central-mcp watch <project>.
Primary surfaces:
- MCP tools (
dispatch,check_dispatch,list_projects,orchestration_history,reorder_projects, …) — defined insrc/central_mcp/server.py. - CLI subcommands (
run,up,tmux,zellij,down,watch,upgrade,add,remove,list,brief,install,alias,unalias,reorder,init,serve) — wired insrc/central_mcp/cli/__init__.py, implementation insrc/central_mcp/cli/_commands.py.
Repo layout
src/central_mcp/
cli/
__init__.py argparse + entry point (`central-mcp`, `cmcp`)
_commands.py cmd_* handlers + shared helpers
adapters/base.py per-agent launch / session-list logic
server.py MCP tool definitions (stdio)
registry.py registry.yaml load / save / reorder
layout.py tmux multi-pane layout builder
zellij.py zellij KDL layout builder
grid.py shared terminal-size-derived pane math (tmux + zellij)
watch.py `central-mcp watch` jsonl streamer
session_info.py which-multiplexer-is-active stamp
paths.py $CENTRAL_MCP_HOME resolution cascade
data/
CLAUDE.md RUNTIME orchestrator guideline (shipped)
AGENTS.md RUNTIME orchestrator guideline (shipped)
tests/ pytest suite (run: `uv run --no-sync pytest`)
docs/
ROADMAP.md phases / intent
architecture/ deeper dives (gemini session storage, etc.)
CHANGELOG.md Keep-a-Changelog; top block = unreleased when in-flight
pyproject.toml `version = "X.Y.Z"` (hatchling)
README.md / README_KO.md user-facing docs; absolute image URLs so PyPI renders them
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.
- 3d ago First seen · 86 lines · 1,742 tokens per session scan C 5d7c290d111d
central-mcp AGENTS.md is an instructions file published in the GitHub repository andy5090/central-mcp (5 stars, last pushed 22d ago), licensed MIT. It adds 1,742 tokens to every session, about $0.0087 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
good-bad-ugly AGENTS.md
AGENTS.md instructions for XyndoX/good-bad-ugly, covering good-bad-ugly — tiered multi-agent orchestration, tiers, the loop, big features: spec → plan → execute and external-system discipline.
workflow AGENTS.md
AGENTS.md instructions for vercel/workflow, covering agent instructions, architecture, core components, workflow execution model and development commands.
NEEDLE CLAUDE.md
Instructions for jedarden/NEEDLE, covering needle project conventions, msrv, module dependency graph, code style and testing.
a-i--skills 03-development-workflow.instructions.md
Instructions for organvm-iv-taxis/a-i--skills, covering development workflow instructions, no repo-wide build system, common development commands, after adding/modifying skills and validation before committing.
a-i--skills 02-skill-format.instructions.md
Instructions for organvm-iv-taxis/a-i--skills, covering skill format instructions, skill.md file structure, required yaml frontmatter, optional yaml fields and naming rules.
MindFlock AGENTS.md
Instructions for MindFlock/MindFlock, covering mindflock — agent onboarding, setup and tests, map and conventions.