doc-reviewer

doc-reviewer is a skill for Claude Code, Codex from sfc-gh-myoung/ai_coding_rules. It costs 57 tokens per session (3,253 once invoked), scanned A, original, Apache-2.0.

A documentation review tool for checking project documents such as READMEs and files in docs/. It examines accuracy, completeness, clarity, structure, links, commands, and whether references are still current.

In plain words
What is it for?
Use it for full, focused, or staleness reviews of one document or a collection of documents. It can verify file references, test commands, and links.
Why use it?
It helps catch documentation that no longer matches the codebase or leads users through broken steps. This makes project instructions more dependable.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it for full, focused, or staleness reviews of one document or a collection of documents. It can verify file references, test commands, and links.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sfc-gh-myoung/ai_coding_rules/doc-reviewer
Install

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.

Any agent
npx skills add sfc-gh-myoung/ai_coding_rules --skill doc-reviewer
Clone the repo
git clone --depth 1 https://github.com/sfc-gh-myoung/ai_coding_rules

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for doc-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/skills/sfc-gh-myoung/ai_coding_rules/doc-reviewer/github.svg)](https://agentmods.dev/skills/sfc-gh-myoung/ai_coding_rules/doc-reviewer)
Your own site
<a href="https://agentmods.dev/skills/sfc-gh-myoung/ai_coding_rules/doc-reviewer"><img src="https://agentmods.dev/badge/skills/sfc-gh-myoung/ai_coding_rules/doc-reviewer/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.

agentmods 80×15 button for doc-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/skills/sfc-gh-myoung/ai_coding_rules/doc-reviewer"><img src="https://agentmods.dev/badge/skills/sfc-gh-myoung/ai_coding_rules/doc-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,253 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.03253
Opus 5 $0.00028 $0.01626
Sonnet 5 $0.00011 $0.00651
Haiku 4.5 $0.00006 $0.00325

Measured 11d ago against content hash 1d4659b82924, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

doc-reviewer 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.

The scan reads SKILL.md. This mod also ships 2 executable files (tests/test_doc_reviewer_gate7_integration.py, tests/test_doc_reviewer_per_dimension_timing.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/doc-reviewer/SKILL.md · 328 lines

How it starts

The opening of the file, as written. The whole thing — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Documentation Reviewer

Purpose

Review project documentation for accuracy with codebase, completeness of coverage, clarity for users, consistency with conventions, staleness of references, and logical structure. Uses a 6-dimension rubric optimized for user success.

Use this skill when

  • Review documentation (README, CONTRIBUTING, docs/*.md)
  • Conduct FULL / FOCUSED / STALENESS documentation review
  • Verify documentation is current with the codebase
  • Check for broken links or outdated references

Inputs

Required:

  • review_date: YYYY-MM-DD
  • review_mode: FULL | FOCUSED | STALENESS
  • model: Model slug (e.g., claude-sonnet-45)

Optional:

  • target_files: List of file paths (defaults to project docs if not specified)
  • review_scope: single | collection (default: single)
  • focus_area: Required if review_mode is FOCUSED. If FOCUSED mode and focus_area missing: STOP, report error Missing required input: focus_area for FOCUSED mode
  • output_root: Root directory for output files (default: reviews/). Subdirectories doc-reviews/ or summaries/ appended automatically. Supports relative paths including ../.
  • overwrite: true | false (default: false) - If true, overwrite existing review file. If false, use sequential numbering (-01, -02, etc.)
  • timing_enabled: true | false (default: false — doc-reviewer retains its current opt-in default; the per-dimension timing pipeline added in v2.2.0 is wired up but not yet universally enabled. When set to true, Step 4a checkpoint pairs and Gate 7 apply.)
  • execution_mode: parallel (default, 6 sub-agents) | sequential - Execution strategy for dimension evaluation

Default Target Files

When target_files not specified, reviews:

  • ./README.md - Project overview and setup
  • ./CONTRIBUTING.md - Contribution guidelines
  • ./docs/*.md - All documentation files in docs/ folder

Outputs

Single scope (per-file): {output_root}/doc-reviews/<doc-name>-<model>-<YYYY-MM-DD>.md

Read the full file on GitHub · 328 lines

Changes

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.

  1. 11d ago First seen · 328 lines · 57 tokens per session scan A 1d4659b82924

Subscribe to this mod's changes

doc-reviewer is a skill published in the GitHub repository sfc-gh-myoung/ai_coding_rules (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 3,253 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens