multi-agent-governance

multi-agent-governance is a skill for Claude Code, Codex from levelsofself/mcp-nervous-system. It costs 51 tokens per session (945 once invoked), scanned A, original, MIT.

A governance guide for systems where multiple AI agents work together. It covers shared roles, enforced rules, drift checks, and append-only records of actions and decisions.

In plain words
What is it for?
It is for designing or auditing multi-agent systems with central configuration, behavioral checks, change tracking, and file-based memory.
Why use it?
It helps teams track responsibility and detect when agents, configurations, or roles move away from their intended setup.

Skill for Claude CodeCodex

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 skills/levelsofself/mcp-nervous-system/multi-agent-governance
Any agent
npx skills add levelsofself/mcp-nervous-system --skill multi-agent-governance
Clone the repo
git clone --depth 1 https://github.com/levelsofself/mcp-nervous-system

Made for: Claude Code, Codex.

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.

agentmods badge for multi-agent-governance

README.md
[![agentmods](https://agentmods.dev/badge/skills/levelsofself/mcp-nervous-system/multi-agent-governance.svg)](https://agentmods.dev/skills/levelsofself/mcp-nervous-system/multi-agent-governance)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 945 The whole file, excluding the scripts and references it only reads on demand.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00051 $0.00945
Opus 5 $0.00026 $0.00473
Sonnet 5 $0.00010 $0.00189
Haiku 4.5 $0.00005 $0.00094

Measured 5d ago against content hash 3b1cef94b4da, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 5d 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.

skills/multi-agent-governance/SKILL.md · 98 lines

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

  1. Single source of truth - One config file defines all agent roles. Every agent reads from it. No parallel systems.
  2. Behavioral enforcement - Rules are not suggestions. Guardrails are enforced through preflight checks, violation logging, and automated audits.
  3. 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.
  4. Tamper-proof audit trails - Every action, every change, every decision is logged in append-only logs that can be verified for integrity.
  5. 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:

  1. Check if the file is on the protected list
  2. If protected: log the attempt, report to admin, and STOP
  3. 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?

Read the full file on GitHub · 98 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.

  1. 5d ago First seen · 98 lines · 51 tokens per session scan A 3b1cef94b4da

Subscribe to this mod's changes

multi-agent-governance is a skill published in the GitHub repository levelsofself/mcp-nervous-system (4 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 945 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

agt-policy-authoring

Create and validate a minimal AGT Copilot CLI policy tailored to the repository being inspected.

microsoft/agent-governance-toolkit · 23 tokens

database-engineer

SQLite database expertise for migrations, multi-tenant patterns, transactional safety, FTS5 virtual tables, and schema evolution. Use this skill for ANY work involving schema changes, data migrations, INSERT/UPSERT semantics, FTS5 rebuilds, transaction rollback design, multi-tenant data isolation, or SQLite…

Vinix24/vnx-orchestration · 0 tokens

intelligence-engineer

VNX-specific domain expertise for the intelligence system, central state databases, and dispatch lifecycle. Use when working on qualityintelligence.db / runtimecoordination.db / dispatchtracker.db, codesnippets FTS5, snippetmetadata linkage, successpatterns / antipatterns, T0 state projection (t0state.json)…

Vinix24/vnx-orchestration · 0 tokens

fabric-reference

Read-only runbook for how the VNX fabric actually works — state resolution, the single-entry dispatch door, gate invocation, the horizon planning layer, the plan-gate panel, and the hard gotchas that repeatedly bite (PATH-break, dual-CLI, codex-cert, classifier-protected actions). Use when you need to look up a fabric…

Vinix24/vnx-orchestration · 116 tokens

featureplan-kickoff

VNX feature-execution kickoff preflight. USE THIS when starting or resuming a feature or track from its plan: checking worktree/queue/staging health, finding the first promoteable dispatch, and handing off to @t0-orchestrator. Reads the feature's track + plan doc from Horizon's tracks DB (vnx horizon, alias vnx…

Vinix24/vnx-orchestration · 99 tokens

monitoring-specialist

System monitoring, alerting, and observability implementation.

Vinix24/vnx-orchestration · 15 tokens