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 skills add levelsofself/mcp-nervous-system --skill multi-agent-governancegit clone --depth 1 https://github.com/levelsofself/mcp-nervous-systemWrote 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.
[](https://agentmods.dev/skills/levelsofself/mcp-nervous-system/multi-agent-governance)<a href="https://agentmods.dev/skills/levelsofself/mcp-nervous-system/multi-agent-governance"><img src="https://agentmods.dev/badge/skills/levelsofself/mcp-nervous-system/multi-agent-governance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/levelsofself/mcp-nervous-system/multi-agent-governance"><img src="https://agentmods.dev/badge/skills/levelsofself/mcp-nervous-system/multi-agent-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00051 | $0.00945 |
| Opus 5.5 | $0.00020 | $0.00378 |
| Sonnet 5.5 | $0.00010 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
multi-agent-governance 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Agent Governance
Governance patterns for multi-agent AI systems. When you have multiple autonomous AI agents operating together, you need accountability, behavioral enforcement, and drift detection - just like human organizations.
Core Principles
- Single source of truth - One config file defines all agent roles. Every agent reads from it. No parallel systems.
- Behavioral enforcement - Rules are not suggestions. Guardrails are enforced through preflight checks, violation logging, and automated audits.
- Drift detection - Systems drift from their intended state over time. Automated drift audits catch configuration mismatches, version inconsistencies, and role conflicts before they cause failures.
- Tamper-proof audit trails - Every action, every change, every decision is logged in append-only logs that can be verified for integrity.
- File-based memory - Agent memory lives in files on disk, not in cloud databases. This enables air-gapped deployment, full auditability, and zero vendor dependency.
Governance Patterns
Role Management
Define roles in a single JSON file that all agents reference:
{
"agent-name": {
"role": "Operations Manager",
"scope": ["dispatch", "monitoring", "reporting"],
"access": "admin",
"model": "claude-opus-4-6"
}
}
Every agent reads from this file at startup. Changes propagate automatically.
Preflight Checks
Before any agent modifies a file:
- Check if the file is on the protected list
- If protected: log the attempt, report to admin, and STOP
- If allowed: create backup, make change, syntax check, restart affected process
Drift Audit Scopes
Run periodic audits across these dimensions:
- roles - Do running agents match their role definitions?
- versions - Are all agents on the correct model version?
- files - Have any protected files been modified?
- processes - Are all expected processes running?
- config - Do config files match expected state?
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.
- 1mo ago First seen · 98 lines · 51 tokens per session scan A 3b1cef94b4da
multi-agent-governance is a skill published in the GitHub repository levelsofself/mcp-nervous-system (4 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 945 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
agt-policy-authoring
Create and validate a minimal AGT Copilot CLI policy tailored to the repository being inspected.
rotate
Saves this session's state as a handover so a fresh session can continue after /clear, or picks up an earlier handover. Use when the context-rotation guard asks for a handover, when the user types /context-rotation:rotate, or when the user wants to continue from the work of an earlier session.
orchestrate
This is the extended reference for the headless T0 orchestrator. The condensed identity is in agents/orchestrator/CLAUDE.md.
gnt-check-action
Check a side-effectful action against this organization's approved gnt rules before taking it, and stop on a blocked or needshuman verdict.
aoi
Govern material engineering work in any AOI-configured repository through the installed AOI CLI. Use when AOI hooks report an active project, before edits or external actions, and when planning, claiming, delegating, verifying, checkpointing, delivering, or closing AOI tasks.
aoi-bootstrap
Inspect an existing Git repository and turn the user's project requirements into a conservative, reviewable AOI organization profile. Use when the user asks to initialize AOI, create or review aoi.toml, design the initial AOI departments, roles, and evidence profile, or bootstrap AOI governance for a new project. Do…