Borrowing it
Nothing to install: this file belongs to managedcode/dotPilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/managedcode/dotPilot/main/.codex/skills/mcaf-solution-governance/SKILL.mdgit clone --depth 1 https://github.com/managedcode/dotPilotWrote 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/managedcode/dotpilot/mcaf-solution-governance)<a href="https://agentmods.dev/skills/managedcode/dotpilot/mcaf-solution-governance"><img src="https://agentmods.dev/badge/skills/managedcode/dotpilot/mcaf-solution-governance.svg" alt="Measured on agentmods" 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.00064 | $0.01019 |
| Opus 5 | $0.00032 | $0.00509 |
| Sonnet 5 | $0.00013 | $0.00204 |
| Haiku 4.5 | $0.00006 | $0.00102 |
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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mcaf-solution-governance — 92% identical, 21 lines differ
How it starts
The opening of the file, as written. The whole thing — 117 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.
- 3d ago First seen · 117 lines · 64 tokens per session scan A 10acda404da0
mcaf-solution-governance is a skill published in the GitHub repository managedcode/dotPilot (23 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 1,019 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-09-03.
Other skills, from other repositories
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.
performance-optimization
Measure-first performance work. Use on triggers like "it's slow", "profile this", "optimize perf", "fix the bottleneck", "improve load time / Core Web Vitals", or when a measured regression needs fixing. Enforces measure-before-optimize. Fills a perf gap not covered by existing project skills. Not a build/ship…
node-inspect-debugger
See runtime state a console.log cannot reach — set real breakpoints, step, and dump the scope chain of a paused Node/TypeScript process. Use on "set a breakpoint", "inspect runtime state", "console.log isn't enough", "step through this", "what's in this closure at runtime", "attach a debugger". Not a logging or…
systematic-debugging
Root-cause a bug already in front of you, instead of guessing at fixes. Use on triggers like "root cause this", "why is this failing", "debug systematically", "this test is flaky", "it works locally but not in CI", or when a fix attempt has already failed once. Enforces a phased evidence-first process before any code…
code-quality
Drive static-analysis code quality in pi-agent-dashboard with Biome (analyze → fix → test), in changed-files or whole-repo mode. Use when asked to "improve code quality", "lint and fix", "clean up warnings", "fix Biome issues", "run static analysis", or when setting a code-quality goal. Skip for one-line edits.
Research Synthesis Workflow
A step-by-step guide to synthesizing research from multiple sources into a coherent summary.