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 skills/managedcode/mcpgateway/mcaf-solution-governancenpx skills add managedcode/MCPGateway --skill mcaf-solution-governancegit clone --depth 1 https://github.com/managedcode/MCPGatewayWhat 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.00064 | $0.00982 |
| Opus 5 | $0.00032 | $0.00491 |
| Sonnet 5 | $0.00013 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
mcaf-solution-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 2d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCAF: Solution Governance
Trigger On
- bootstrap or rewrite a repo-wide
AGENTS.md - add project-local
AGENTS.mdfiles for a multi-project solution - clarify rule precedence, skill routing, or maintainability policy placement
Value
- produce a concrete project delta: code, docs, config, tests, CI, or review artifact
- reduce ambiguity through explicit planning, verification, and final validation skills
- leave reusable project context so future tasks are faster and safer
Do Not Use For
- writing feature specs or ADR content
- code-level refactoring without a governance change
Inputs
- current repo topology and module roots
- existing root or local
AGENTS.mdfiles - actual build, test, format, and analyze commands
- the active stack when commands or tooling are platform-specific
Quick Start
- Read the nearest
AGENTS.mdand confirm scope and constraints. - Run this skill's
Workflowthrough theRalph Loopuntil outcomes are acceptable. - Return the
Required Result Formatwith concrete artifacts and verification evidence.
Workflow
- Identify the solution root and any project or module roots that need their own
AGENTS.md. - Keep the root file global:
- shared workflow
- shared commands
- rule precedence
- global skill list
- maintainability-limit keys
- Keep local files narrow:
- project purpose
- entry points
- boundaries
- local commands
- applicable skills
- stricter local constraints
- Resolve overlap explicitly. Local rules may be stricter or more specific, never silently weaker.
- When the stack is .NET, record:
- the test framework
- the runner model (
VSTestorMicrosoft.Testing.Platform) - the repo-root
.editorconfigas the analyzer config owner
- Put numeric maintainability limits in
AGENTS.md, not in framework prose or skill bodies.
Deliver
- one clear root
AGENTS.md - local
AGENTS.mdfiles only where boundaries justify them - explicit precedence rules and skill-routing guidance
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 114 lines · 64 tokens per session scan A ab98e920b442
mcaf-solution-governance is a skill published in the GitHub repository managedcode/MCPGateway (5 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 982 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.
Other skills, from other repositories
t2i
Use the t2i CLI to generate AI images from text prompts via Microsoft Foundry providers (FLUX.2, MAI-Image-2). Activate when the user asks to generate images, automate image creation in scripts, or set up image generation for CI/CD.
performance-tracking
Status: Active Domain: Diagnostics, SLA Validation, Benchmarking Created: 2026-04-28 Author: Rachael (CLI/UX Dev).
benchmark-parity-triage
Use this when a benchmark harness exists but parity with an upstream reference implementation is unproven.
cli-wiring
Bug class: Commands implemented in packages/squad-cli/src/cli/commands/ but never routed in cli-entry.ts.
init-mode
Team initialization flow (Phase 1 proposal + Phase 2 creation).
distributed-mesh
How to coordinate with squads on different machines using git as transport.