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 security-scangit 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/security-scan)<a href="https://agentmods.dev/skills/jason21wc/ai-governance-mcp/security-scan"><img src="https://agentmods.dev/badge/skills/jason21wc/ai-governance-mcp/security-scan/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/security-scan"><img src="https://agentmods.dev/badge/skills/jason21wc/ai-governance-mcp/security-scan.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.00081 | $0.00458 |
| Opus 5 | $0.00041 | $0.00229 |
| Sonnet 5 | $0.00016 | $0.00092 |
| Haiku 4.5 | $0.00008 | $0.00046 |
Grade A, and why
security-scan 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.
What it actually says
Runtime Context
After the skill loads, establish the project root, branch, dependency manifests, and relevant authentication/configuration surfaces with ordinary read-only calls.
Instructions
You are running a focused security scan. Collect the Runtime Context above, then read procedure.md in this skill folder for the full scanning protocol.
Scope
This skill covers the most mechanical, portable security concerns:
- Secrets detection — API keys, tokens, passwords, private keys in code and config
- Dependency audit — known vulnerabilities in project dependencies
- Basic auth patterns — hardcoded credentials, default passwords, missing auth
For deeper analysis (full OWASP systematic review, attack surface mapping, data flow tracing), perform a comprehensive manual security review with project-specific context.
Execution Protocol
- Read
procedure.mdfor the full scanning procedure. - Execute all three scan phases in order.
- Present findings with severity gating — CRITICAL and HIGH findings first.
- Every finding needs evidence — file:line + quoted code, or it's dropped.
Portability Note
Slash-command references (e.g. /code-review) name companion skills. On hosts where a named skill isn't installed, perform the equivalent manually instead of invoking it.
Output Defaults
- Severity gating: CRITICAL and HIGH shown prominently; MEDIUM and LOW summarized
- Evidence required: Every finding must cite
file:line+ quoted code - Actionable fixes: Each finding includes a specific remediation step
What ships with it
1 file 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 · 41 lines · 81 tokens per session scan A fbae17834224
security-scan is a skill published in the GitHub repository jason21wc/ai-governance-mcp (0 stars, last pushed 10d ago), licensed Apache-2.0. It adds 81 tokens to every session and 458 once invoked, about $0.0004 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…
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…