Borrowing it
Nothing to install: this file belongs to managedcode/MCPGateway. 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/MCPGateway/main/.codex/skills/mcaf-source-control/SKILL.mdgit clone --depth 1 https://github.com/managedcode/MCPGatewayWrote 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/mcpgateway/mcaf-source-control)<a href="https://agentmods.dev/skills/managedcode/mcpgateway/mcaf-source-control"><img src="https://agentmods.dev/badge/skills/managedcode/mcpgateway/mcaf-source-control/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/managedcode/mcpgateway/mcaf-source-control"><img src="https://agentmods.dev/badge/skills/managedcode/mcpgateway/mcaf-source-control.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.00050 | $0.00761 |
| Opus 5.5 | $0.00020 | $0.00304 |
| Sonnet 5.5 | $0.00010 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
mcaf-source-control 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 1mo 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.
This is a copy
92% identical to dotnet-mcaf-source-control — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCAF: Source Control
Trigger On
- bootstrapping source-control policy
- tightening branch, merge, or PR rules
- documenting commit or release hygiene
- dealing with secrets-in-git or repository structure issues
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
- CI/CD workflow design with no source-control policy change
- one-off git commands that do not alter repo policy
Inputs
- current branching and merge flow
- release strategy and versioning expectations
- secret-handling and repository-structure constraints
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
- Agree on merge and release strategy before scaling implementation.
- Keep branch and PR rules explicit in-repo.
- Treat secrets in git history as a critical incident, not cleanup noise.
- Use concrete policy language, not hand-waving.
Deliver
- clear branch and merge strategy
- updated contribution or governance docs
- safer repository hygiene around commits, PRs, and secrets
Validate
- naming and merge rules are explicit
- release/versioning implications are documented where needed
- secret hygiene is treated as policy, not tribal knowledge
Ralph Loop
Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.
- Plan first (mandatory):
- analyze current state
- define target outcome, constraints, and risks
- write a detailed execution plan
- list final validation skills to run at the end, with order and reason
- Execute one planned step and produce a concrete delta.
- Review the result and capture findings with actionable next fixes.
- Apply fixes in small batches and rerun the relevant checks or review steps.
- Update the plan after each iteration.
- Repeat until outcomes are acceptable or only explicit exceptions remain.
- If a dependency is missing, bootstrap it or return
status: not_applicablewith explicit reason and fallback path.
What ships with it
2 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.
- 1mo ago First seen · 95 lines · 50 tokens per session scan A 5a0e24a813c6
mcaf-source-control is a skill published in the GitHub repository managedcode/MCPGateway (5 stars, last pushed 8d ago), licensed MIT. It adds 50 tokens to every session and 761 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to dotnet-mcaf-source-control, differing in 25 lines, and is treated as a copy.
Other skills, from other repositories
safe-github-push
A workflow for safely pushing Git repositories that contain large assets or binary files to GitHub. It checks repository changes and file sizes before planning commits and pushes.
changelog
Auto-generate changelog from git commits — grouped by feat/fix/docs with PR links.
release-process
Step-by-step release checklist for Squad — prevents v0.8.22-style disasters.
git-workflow
Squad branching model: dev-first workflow with insiders preview channel.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.