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 m3taz-ahmed/ai-globals --skill agent-governance-lordgit clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/agent-governance-lord)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/agent-governance-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/agent-governance-lord/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/m3taz-ahmed/ai-globals/agent-governance-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/agent-governance-lord.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.00049 | $0.01528 |
| Opus 5 | $0.00024 | $0.00764 |
| Sonnet 5 | $0.00010 | $0.00306 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
agent-governance-lord 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Governance Lord
[OBJ] Runtime governance for AI coding agents: intercept, allowlist, and audit every agent action.
Problem
AI agents can write, push, and deploy without human review at each step. Access control answers "can the agent do this?" — governance answers "should the agent do this?" Permission is necessary; it is not sufficient. An agent can be fully permitted and still wrong.
Rules
- [REQ] Gateway on the path. Every LLM request and MCP tool call MUST pass through
runtime/agent_gateway.py(pre-LLM + post-execution guardrails). No bypass. - [REQ] Three verdicts. Guardrails emit ALLOW / REDACT / BLOCK. Most severe wins (BLOCK > REDACT > ALLOW). Never silently drop a BLOCK.
- [REQ] Pre-LLM guardrails. Inspect outbound prompt + tool payloads BEFORE the model sees them. Catch: secret leakage, prompt injection in tool responses fed back, forbidden tool calls.
- [REQ] Post-execution guardrails. Inspect inbound response + generated code BEFORE the developer sees it. Catch: destructive commands, insecure patterns, hallucinated APIs.
- [REQ] Agent allowlist. Only agents registered in
runtime/agent_catalog.pywithstatus == ALLOWEDmay run. Unknown agent = BLOCK + alert. - [REQ] Flow allowlist. Each agent has an
allowed_flowslist. A flow not in the list = BLOCK. No blanket flow access. - [REQ] Model allowlist. Each agent has an
allowed_modelslist. A model not in the list = BLOCK. Prevents unauthorized model escalation. - [REQ] MCP-as-securable. MCP servers registered in
runtime/mcp_securable.pyas governed assets. Access via GRANT policies (USE/ADMIN/REGISTER). No ungoverned MCP server. - [REQ] Composite identity. Every agent action attributed to BOTH agent + human principal (
runtime/composite_identity.py). No anonymous agent actions. - [REQ] Audit every verdict. Every ALLOW/REDACT/BLOCK logged with agent_id, user_id, tool, reason. Tamper-evident via existing audit chain.
- [REQ] Rate limiting. Per-agent rate limits enforced at the gateway. Burst > threshold = BLOCK + cooldown.
- [REQ] Cost attribution. Per-agent cost tracked via
runtime/cost_attribution.py. Anomaly (spike/budget breach) = alert + optional throttle. - [REQ] Plan validation. Before edits, validate the agent's plan via
runtime/plan_diff_validator.py. Forbidden paths = BLOCK. File count > max = WARN. - [REQ] Diff validation. After edits, validate the git diff. Undeclared imports = WARN. Test gap = WARN. Unrelated refactor = WARN.
- [REQ] Supply-chain guard. New imports not in lockfile = WARN. External package not declared = BLOCK in strict mode.
- [REQ] Human-in-the-loop. Irreversible/destructive actions (rm, drop, force-push, deploy to prod) require explicit human approval. Gateway holds the action pending approval.
- [REQ] Rollback path. Every agent action that modifies state must have a documented rollback. No rollback = BLOCK.
- [PROHIBIT] Bypassing the gateway for "trusted" agents. All agents pass through.
- [PROHIBIT] Allowing an agent to call an ungoverned MCP server.
- [PROHIBIT] Executing a destructive action without composite identity attribution + human approval.
- [REQ] SARC enforcement sites. Implement 4 enforcement sites: Pre-Action Gate (block injection/PII/policy violations before LLM call), Action-Time Monitor (rate/cost/budget enforcement, circuit breakers), Post-Action Auditor (log, evaluate, score for reliability@k), Escalation Router (human approval, kill-switch, incident creation).
- [REQ] Agent SRE Governance v1.0. Implement SLOs, error budgets, circuit breakers, chaos engineering, trace replay, Ed25519 artifact signing, SBOMs, and OpenTelemetry for all agent deployments. Reference: Microsoft Agent Governance Toolkit.
- [REQ] Microsoft Agent Hooks. Support framework-neutral governance contracts — "deny means deny" enforceable across LangChain, CrewAI, OpenAI Agents SDK, etc.
- [REQ] MCP 2026-07-28 stateless governance. Update gateway for stateless MCP protocol. No session state assumptions. Per-request protocolVersion validation. Header-based routing (Mcp-Method, Mcp-Name).
- [REQ] Per-PR spend limits. Implement per-PR spend caps (soft block) and org-level ACU visibility. Devin enterprise pattern.
- [REQ] Enterprise MCP server allowlist. Maintain allowlist of approved MCP servers. Block ungoverned servers. Enterprise plugin governance (required/optional/forbidden plugins).
- [REQ] 5-layer control plane. Gateway Layer (auth, rate limiting, cost tracking) → Policy Layer (4-level hierarchy, fail-closed) → Observability Layer (tamper-evident audit) → Governance Layer (approvals, kill-switch, RBAC) → Integration Layer (A2A, MCP, REST, webhooks).
- [PROHIBIT] Deploying agents without SARC 4-site enforcement and Agent SRE Governance compliance.
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 Changed · +8 lines f54db7e0ecfa
- 12d ago First seen · 75 lines · 49 tokens per session scan A d98e5cecbe5a
agent-governance-lord is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 1,528 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…