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 agentmods add skills/no-product/knowledgebase-mcp/example-reviewnpx skills add NO-Product/knowledgebase-mcp --skill example-reviewgit clone --depth 1 https://github.com/NO-Product/knowledgebase-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/no-product/knowledgebase-mcp/example-review)<a href="https://agentmods.dev/skills/no-product/knowledgebase-mcp/example-review"><img src="https://agentmods.dev/badge/skills/no-product/knowledgebase-mcp/example-review.svg" alt="Measured on agentmods" 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 | $0.00003 | $0.00155 |
| Opus 5 | $0.00002 | $0.00077 |
| Sonnet 5 | $0.00001 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
Example Documentation Review 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 3d 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
Example Documentation Review
Use this skill to review a technology documentation source before publishing it. Check that the overview explains when to use the source, topics are named predictably, and search summaries contain the terms an agent is likely to use.
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.
- 3d ago First seen · 22 lines · 3 tokens per session scan A 3e15acda7679
Example Documentation Review is a skill published in the GitHub repository NO-Product/knowledgebase-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 3 tokens to every session and 155 once invoked, about $0.0000 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
Agent Instruction Drift Check
Procedure for comparing an agent-facing instruction doc (AGENTS.md/CLAUDE.md-style) against the actual current code and configuration to find and flag mismatches.
yapper
Yapper forces AI responses to be maximally verbose, thoroughly elaborated, and exhaustively explained. All output is expanded by 200–400%. Technical accuracy is maintained at 100%. This plugin is the structural and philosophical inverse of compression-based plugins.
grill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
ai-tells-review
Use when public prose still sounds machine-written after ai-tells-scan. Complements ai-tells-scan's mechanical pass with structural judgment: rhythm, hedging, rhetorical reflexes, and performative emphasis. Trigger on 'review for AI tells,' 'does this read AI,' 'strip the AI smell,' or 'make this less AI.'.
doc-architecture-review
Evaluate documentation information architecture: navigation paths, discoverability, progressive disclosure, cross-linking, and mental model alignment. This skill should be used when restructuring docs, adding new sections, or when users report difficulty finding information.
doc-completeness-audit
Audit documentation completeness by mapping what a doc set should cover against what it actually covers. Produces a prioritized gap report by topic, not just by file. This skill should be used after shipping features, before releases, or when users report missing documentation.