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 pleaseai/claude-code-plugins --skill review-docsgit clone --depth 1 https://github.com/pleaseai/claude-code-pluginsWrote 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/pleaseai/claude-code-plugins/review-docs)<a href="https://agentmods.dev/skills/pleaseai/claude-code-plugins/review-docs"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/review-docs/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/pleaseai/claude-code-plugins/review-docs"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/review-docs.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.00108 | $0.03694 |
| Opus 5.5 | $0.00043 | $0.01478 |
| Sonnet 5.5 | $0.00022 | $0.00739 |
| Haiku 4.5 | $0.00011 | $0.00369 |
Grade A, and why
review-docs 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.
This is a copy
100% identical to review-docs — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 480 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Docs
Comprehensive documentation review, optimized for Docus/Nuxt Content but compatible with any Markdown documentation.
Workflow Overview
This skill performs a 5-step review process:
- Detect Project Type - Identify Docus/Nuxt Content vs generic Markdown
- Analyze Structure - Map documentation organization, locales, sections
- Technical Validation - Check frontmatter, MDC syntax (if applicable), file naming
- Content Quality Review - Evaluate clarity, SEO, structure, i18n
- Generate Report - Provide categorized, actionable recommendations
Priority Levels
- Critical - Blocks deployment or causes errors (missing frontmatter, invalid MDC syntax)
- Important - Significantly impacts UX/SEO (poor metadata, passive voice, unclear headings)
- Nice-to-have - Polish and optimization suggestions (add callouts, improve examples)
Expectations
This skill generates a detailed report only. After reviewing, it offers to fix identified issues if requested.
Step 1: Detect Project Type
Goal: Determine if this is a Docus/Nuxt Content project or generic Markdown documentation.
Detection Indicators
Check for Docus/Nuxt Content:
-
package.json dependencies:
"docus"- Docus theme"@nuxt/content"- Nuxt Content module"@nuxtjs/mdc"- MDC support
-
Configuration files:
nuxt.config.tsornuxt.config.jswith@nuxt/contentmodulecontent.config.ts- Content collections configuration
-
Content structure:
content/ordocs/content/directory.navigation.ymlfiles in subdirectories- MDC syntax in markdown files (
::component-name)
-
Project structure:
- Numbered directories (
1.getting-started/,2.guide/) - Frontmatter with
navigation,seofields
- Numbered directories (
Project Type Classification
Type A: Docus/Nuxt Content Project
- All Docus-specific validations apply
- MDC component syntax checks (u- prefix requirement)
- Nuxt Content frontmatter structure
- Navigation files (.navigation.yml)
- Full technical validation
What ships with it
6 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 First seen · 480 lines · 108 tokens per session scan A 4dadf688ddd1
review-docs is a skill published in the GitHub repository pleaseai/claude-code-plugins (16 stars, last pushed 5d ago), licensed MIT. It adds 108 tokens to every session and 3,694 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to review-docs, differing in 0 lines, and is treated as a copy.
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…