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 nthnclrk/enablement-skills --skill content-governance-systemgit clone --depth 1 https://github.com/nthnclrk/enablement-skillsWrote 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/nthnclrk/enablement-skills/content-governance-system)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/content-governance-system"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/content-governance-system/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/nthnclrk/enablement-skills/content-governance-system"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/content-governance-system.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.00063 | $0.00931 |
| Opus 5 | $0.00032 | $0.00465 |
| Sonnet 5 | $0.00013 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
content-governance-system 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 11d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content governance system
Design the weekly operating model that keeps enablement content accurate and findable. This is not an inventory. If the team cannot run it every week with the people they have, it is not done.
Fails. "Classify all 400 assets, stand up a content council, and review everything quarterly."
Passes. "Each Wednesday: owners clear due and overdue reviews, intake picks one request, publishers ship only approved versions. Live assets stay published while overdue for review. Urgent launch changes use a 48-hour exception with a named follow-up owner."
A one-time coverage audit and backlog is content-gap-analysis.
Confirm Inputs First
Ask only for the inputs that change the operating model:
- Repositories and content types in scope
- Who already owns accuracy, claim approval, and the right to publish
- Current pain: sprawl, stale claims, unclear source of truth, or blocked launches
- Who will run the weekly cadence, and how much time they actually have
If ownership or system-write authority is unknown, leave it unknown. Do not invent usage.
Read The Right Reference
Read references/governance-model-template.md for the two status axes, approval-vs-publish split, and a weekly cadence you can copy. Read references/source-system-guide.md when the rules must map into publishing systems the team already uses.
Default Workflow
- Name the weekly job. Who meets or reviews, on which day, and what gets decided. Done when a new owner could run next week without a kickoff project.
- Set decision rights. Content approval, publish authorization, and system write are three different rights. A claim owner may approve wording and still lack permission to publish.
- Keep two independent axes.
Publication:
draft,in_review,approved,published,retired. Review:current,due,overdue,blocked. A live asset stayspublishedwhile due or overdue. Review status must not hide it from published denominators. - Trigger review from risk, not a universal calendar. Legal, security, pricing, and product claims review when the source changes or validity ends. Convenience content can wait.
- Define intake that matches capacity. One prioritization path for new requests. No shadow queues. Urgent work uses a time-boxed exception that cannot skip legal or security approval.
- Name the quality checks that can fail a publish. Message accuracy, proof, audience, compliance. Cosmetic checks that nobody enforces do not go in the model.
- Separate canonical source from distribution copies. One content ID and version. Changes happen in the canonical source, then propagate. Do not create a second source of truth to "make it easier to find."
- Scale to the team you have. Unused councils, unused gates, and unused metadata fields are failed governance. Measure current-content rate, orphan rate, and review completion — not a usage number you do not have.
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.
- 11d ago First seen · 74 lines · 63 tokens per session scan A 0597a00f328a
content-governance-system is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 22d ago), licensed MIT. It adds 63 tokens to every session and 931 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-30.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…