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 oakandfeather/ai-assisted-coding-governance --skill govern-initgit clone --depth 1 https://github.com/oakandfeather/ai-assisted-coding-governanceWrote 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/oakandfeather/ai-assisted-coding-governance/govern-init)<a href="https://agentmods.dev/skills/oakandfeather/ai-assisted-coding-governance/govern-init"><img src="https://agentmods.dev/badge/skills/oakandfeather/ai-assisted-coding-governance/govern-init/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/oakandfeather/ai-assisted-coding-governance/govern-init"><img src="https://agentmods.dev/badge/skills/oakandfeather/ai-assisted-coding-governance/govern-init.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.00159 | $0.00841 |
| Opus 5 | $0.00079 | $0.00420 |
| Sonnet 5 | $0.00032 | $0.00168 |
| Haiku 4.5 | $0.00016 | $0.00084 |
Grade A, and why
govern-init 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 8d 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
govern-init
This file is a launcher, not the procedure. The procedure lives in the governance repo at ai-docs/procedures/govern-init.md, and is read fresh from there on every run — so it is current as of the source repo's last git pull, no matter how old this launcher is.
1. Locate the source package
The package lives in the governance repo (ai-docs/). Find it in this order:
- A path the user gives you.
$AI_GOVERNANCE_PATHif set.- Ask. Do not reconstruct the rule files from memory — a paraphrased safety rule is not the safety rule. If you cannot find the source package, stop and say so.
2. Locate the client overlay, if there is one
Some teams keep client masters in a private overlay repo — clients/<client>/profile.md and clients/<client>/policy.md, and no rule files. Find it in this order:
- A path the user gives you.
$AI_GOVERNANCE_CLIENTS_PATHif set.- Prompt for it, and offer to persist it —
[Environment]::SetEnvironmentVariable('AI_GOVERNANCE_CLIENTS_PATH', <path>, 'User')on Windows, a line in the shell profile on macOS/Linux, the same two formsREADME.mddocuments for$AI_GOVERNANCE_PATH.
A missing overlay is not a stop. It is optional, and most engagements have none. Say there is no overlay and carry on — the procedure interviews for the client's rules instead. Do not carry step 1's "stop and say so" posture over to this one; that posture exists because the rule files cannot be reconstructed, and nothing here is a rule file.
3. Read the procedure and follow it
Read ai-docs/procedures/govern-init.md from the resolved source, and follow it exactly. It is the whole procedure — the file set, the banner stripping, the placeholder interview, the client-profile authoring, and the hand-off. Nothing in this launcher supersedes it.
If that file is not there, you are stale — stop. Either this launcher predates the source it is pointed at, or the source predates the split that created ai-docs/procedures/. Show the user what you found, and offer to re-deploy both skills (govern-init and govern-update) from ai-docs/skills/ into ~/.claude/skills/ before proceeding. Do not fall back to scaffolding from memory.
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.
- 8d ago First seen · 35 lines · 159 tokens per session scan A 1fc543e1016f
govern-init is a skill published in the GitHub repository oakandfeather/ai-assisted-coding-governance (2 stars, last pushed yesterday), licensed MIT. It adds 159 tokens to every session and 841 once invoked, about $0.0008 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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…