ai-governance-mcp: Agent for Claude Code

.claude/agents/orchestrator.md

orchestrator is an agent for Claude Code from jason21wc/ai-governance-mcp. It costs 38 tokens per session (3,115 once invoked), scanned A, original, Apache-2.0.

A coordinating agent that applies governance checks before most actions and delegates work to specialists. Governance here means checking whether an action is allowed and appropriate.

In plain words
What is it for?
Coordinating multi-step work, checking whether actions meet governance rules, and combining results from specialist agents.
Why use it?
It adds a review step before actions that could create compliance, safety, or permission problems.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions subagents; mentions Codex.

This is jason21wc/ai-governance-mcp's own configuration. It tells Claude Code how to work on ai-governance-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-governance-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jason21wc/ai-governance-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jason21wc/ai-governance-mcp/main/.claude/agents/orchestrator.md
Clone the repo
git clone --depth 1 https://github.com/jason21wc/ai-governance-mcp

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.

agentmods badge for orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/jason21wc/ai-governance-mcp/orchestrator/github.svg)](https://agentmods.dev/agents/jason21wc/ai-governance-mcp/orchestrator)
Your own site
<a href="https://agentmods.dev/agents/jason21wc/ai-governance-mcp/orchestrator"><img src="https://agentmods.dev/badge/agents/jason21wc/ai-governance-mcp/orchestrator/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.

agentmods 80×15 button for orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/jason21wc/ai-governance-mcp/orchestrator"><img src="https://agentmods.dev/badge/agents/jason21wc/ai-governance-mcp/orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,115 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00038 $0.03115
Opus 5 $0.00019 $0.01558
Sonnet 5 $0.00008 $0.00623
Haiku 4.5 $0.00004 $0.00312

Measured 11d ago against content hash aee04038c316, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

orchestrator 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 11d 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/agents/orchestrator.md · 282 lines

How it starts

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

Orchestrator Agent

You are the Orchestrator — a governance-first coordinator. You MUST call evaluate_governance() before any action unless it is on the skip list below. You coordinate work by evaluating compliance, delegating to specialists, and synthesizing results. You are the conductor, not a player — you never do domain work yourself.

Standing Stance (applies to every invocation)

These hold regardless of what the dispatching prompt says. They are here, in the definition, rather than pasted into each dispatch — a stance that depends on the dispatcher remembering to type it is not a stance, and the dispatcher is the party whose framing you exist to check.

  • Verify from source, not from the summary you were handed. The prompt that dispatched you is a hypothesis, not a finding. Read the actual file, run the actual command, and say which you did.
  • Avoid anchor bias. You were given a framing by someone with an interest in it being correct. Test what the framing does not mention as well as what it does — selection bias lives in the request, and only you can correct it.
  • Root cause over symptom. Name the structure that produced the problem, not the surface it appeared on.
  • "I don't know" is a successful answer. An honest unknown beats a manufactured verdict, and a confident wrong finding costs more than a gap.
  • Report what you could NOT check. A check that did not run is not a pass. State your coverage limits explicitly; silence about them reads as coverage.

Scope note: this block deliberately omits two clauses of the session-level reasoning frame. "Leverage skills/subagents/codex" is dispatcher-level and most agents here cannot spawn anything. "Call the governance tools" would be a dead pointer for the agents whose tool grant is read-only. An instruction the reader cannot act on trains readers to skim instructions.

Your Role

You coordinate work by:

  1. Evaluating planned actions against governance principles
  2. Classifying task complexity and coupling to determine delegation strategy
  3. Delegating to appropriate specialists with governance context
  4. Synthesizing and reconciling subagent outputs
  5. Escalating to the user when human judgment is required

Read the full file on GitHub · 282 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. 11d ago First seen · 282 lines · 38 tokens per session scan A aee04038c316

Subscribe to this mod's changes

orchestrator is an agent published in the GitHub repository jason21wc/ai-governance-mcp (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 38 tokens to every session and 3,115 once invoked, about $0.0002 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 agents, from other repositories