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 content-enhancergit 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/content-enhancer)<a href="https://agentmods.dev/skills/jason21wc/ai-governance-mcp/content-enhancer"><img src="https://agentmods.dev/badge/skills/jason21wc/ai-governance-mcp/content-enhancer/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/content-enhancer"><img src="https://agentmods.dev/badge/skills/jason21wc/ai-governance-mcp/content-enhancer.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.00048 | $0.00966 |
| Opus 5.5 | $0.00019 | $0.00386 |
| Sonnet 5.5 | $0.00010 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
content-enhancer 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Enhancer
Turn supplied material into a useful reference without losing its meaning, visual evidence or origin. Choose the output contract before processing.
Choose the mode
- Enhance (default): improve an existing document while preserving the author's meaning, voice and argument. For substantive restructuring or added context, read procedure.md; use the short path below for simple edits.
- Synthesize: when the user wants a combined reference, comparison or knowledge base, organize attributed evidence across sources. Read synthesis.md. Do not manufacture a common author or consensus.
Several input files do not by themselves select synthesis: a primary article plus supporting material can still be an enhancement. Infer the mode from the requested result, state it briefly, and ask only if a material ambiguity remains. Do not load the other mode's procedure unless the task actually needs both.
Short path for simple text edits
For self-contained pasted text returned in chat, with no added facts: preserve the author's claims, qualifiers, examples and voice; improve the requested wording/organization; compare against the original and return the requested text. Do not load extraction or gap-filling procedures, create files or add a source ledger. Mention only material limitations or a useful brief change note. If the task develops factual gaps or substantial restructuring, load the enhancement procedure then.
Shared workflow
- Establish source location, audience and intended use from the request.
Call
evaluate_governance(planned_action="content enhancement")before writes when that tool is available. Its absence does not revoke user authorization. - For file/URL inputs, visuals, or a durable source bundle, read source-handling.md. A short pasted-text edit needs no extraction tools, manifest, source IDs or extra files.
- Carry out the selected mode. Preserve source qualifiers and distinguish attribution from verification: faithfully repeating a claim does not prove it.
- Verify consequential claims against the actual source passage or figure, including units, exceptions, scope and locator. A citation's presence is not evidence that it supports the associated claim.
- Deliver the artifact with any material coverage limits or unresolved gaps.
Simple edits do not require a coverage report. For artifact-producing tasks,
use the user's output location; otherwise use
enhanced/{slug}/index.mdwith relative links to needed assets. Keep reusable content separate from task-specific operating policies or application code.
What ships with it
7 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 Changed · -68 lines · -13 tokens per session 86e1fb3369f4
- 1mo ago Changed · -1 lines a980146dacb4
- 2mo ago First seen · 154 lines · 61 tokens per session scan A cba423e27f0a
content-enhancer is a skill published in the GitHub repository jason21wc/ai-governance-mcp (0 stars, last pushed 25d ago), licensed Apache-2.0. It adds 48 tokens to every session and 966 once invoked, about $0.0002 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…