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 jason21wc/ai-governance-mcp --skill start-worktreegit clone --depth 1 https://github.com/jason21wc/ai-governance-mcpWrote 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/jason21wc/ai-governance-mcp/start-worktree)<a href="https://agentmods.dev/skills/jason21wc/ai-governance-mcp/start-worktree"><img src="https://agentmods.dev/badge/skills/jason21wc/ai-governance-mcp/start-worktree/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/jason21wc/ai-governance-mcp/start-worktree"><img src="https://agentmods.dev/badge/skills/jason21wc/ai-governance-mcp/start-worktree.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.00070 | $0.00398 |
| Opus 5 | $0.00035 | $0.00199 |
| Sonnet 5 | $0.00014 | $0.00080 |
| Haiku 4.5 | $0.00007 | $0.00040 |
Grade A, and why
start-worktree 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 10d 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.
What it actually says
Start Worktree
Read procedure.md completely, identify the actual host, and follow that host's
adapter. The load-bearing behavior lives in the scripts beside this file:
preflight.shverifies exact local/worktree/live-remote name surfaces and base freshness.prepare.shcreates or adopts a checkout through recorded, retryable transitions and detects duplicate task intent across isolated paths.cleanup.shrefuses removal until ownership, durability, completeness, ignored-file, and cleanliness checks pass; a coherent v2 owner can acknowledge finalization atomically without--force.
Do not replace a failed or unavailable script with remembered Git commands. An unrun check is not a pass. Report the script's exit code and findings.
The invariant is one mutating session per checkout and per wt/* topic branch.
Task keys detect two isolated sessions doing the same work; they do not replace
that checkout isolation or create a global lock.
A Git worktree isolates tracked files, the index, HEAD, and branch; it does not
isolate ports, databases, daemons, caches, editable installs, ignored files,
user configuration, or symlink targets. Use the optional runtime hooks described
in procedure.md when those shared resources need namespacing.
Host permissions remain separate from skill execution. In particular, a managed Codex profile may permit checkout edits while denying the common Git-directory writes needed for worktree creation, fetch, staging, commits, refs, and cleanup; the Codex CLI adapter documents the ordinary-shell handoff for that case.
What ships with it
4 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.
- 10d ago First seen · 30 lines · 70 tokens per session scan A d595fb69745f
start-worktree is a skill published in the GitHub repository jason21wc/ai-governance-mcp (0 stars, last pushed 10d ago), licensed Apache-2.0. It adds 70 tokens to every session and 398 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…