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/keminghe/common-devx/documentation-reviewnpx skills add KemingHe/common-devx --skill documentation-reviewgit clone --depth 1 https://github.com/KemingHe/common-devxWrote 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/keminghe/common-devx/documentation-review)<a href="https://agentmods.dev/skills/keminghe/common-devx/documentation-review"><img src="https://agentmods.dev/badge/skills/keminghe/common-devx/documentation-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.00052 | $0.01295 |
| Opus 5 | $0.00026 | $0.00647 |
| Sonnet 5 | $0.00010 | $0.00259 |
| Haiku 4.5 | $0.00005 | $0.00129 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Review
Review and correct documentation files for consistency, correctness, and drift. Documentation edits only - no functional code changes.
Temporary persona: Technical editor with expertise in documentation standards and version control.
When to Use This Skill
- Before committing documentation changes
- Auditing docs for staleness or drift
- Reviewing PRs (GitHub) / MRs (GitLab) with documentation updates
- Checking consistency across related files
Process
Step 1: Identify Scope
Determine files to review:
- Single file, directory, or pattern
- Related files (e.g., SKILL.md + README + assets)
Step 2: Apply Checklist
| Dimension | Check For |
|---|---|
| Consistency | Version sync (frontmatter/footer), naming patterns, terminology |
| Correctness | Valid YAML/markdown, working links, accurate paths |
| Completeness | Required sections present, no unfilled placeholders |
| Freshness | Last Updated date, version numbers, changelog entries |
| Characters | QWERTY-only everywhere; no smart quotes, emojis, or special Unicode; no em-dashes or em-dash substitutes (--, --) in prose; use - for clause separation (exceptions: ↑; box drawing for tree output) |
| Inline formatting | _underscore_ italics only; colon outside bold label markers (**Topic**:) |
| Linter | Check IDE/editor linter errors when available |
| Output quality | Hard-wrapped bullets or prose that simulate visual wrapping; sentences broken across hard newlines; orphaned (optional) labels in populated sections; unfilled [placeholder] text; terminology inconsistency; KISS/DRY violations |
Step 3: Check Linter Errors
When linter tooling is available (IDE, markdownlint, etc.):
- Run linter on files in scope
- Include linter errors in findings table
- Distinguish between new errors (introduced by changes) and pre-existing
Common markdown linter catches:
- Missing language specifier on fenced code blocks
- Inconsistent list indentation
- Trailing whitespace or missing final newline
- Invalid link references
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 · 109 lines · 52 tokens per session scan A 328efaac362a
documentation-review is a skill published in the GitHub repository KemingHe/common-devx (10 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 1,295 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.
Other skills, from other repositories
developer-marketing-playbook
Complete developer marketing playbook covering DevRel programs, documentation as marketing, API developer experience, community building, and hackathon strategy. For dev-tool founders who need to reach engineers. Follow @WeiYipei on X.
devrel-playbook
Complete Developer Relations playbook — from community building to documentation strategy to event planning. Covers Discord/Slack management, conference speaking, hackathon sponsorship, and measuring DevRel ROI. By @WeiYipei.
doc-bridge-handoff
Resolve Doc Bridge boundaries before changing code.
Technical Documentation Writer
Write developer documentation that developers actually read. API docs, READMEs, architecture guides, and onboarding docs with clarity and structure.
documentation-writer
Write clear, comprehensive technical documentation. Covers README files, API docs, tutorials, architecture guides, and documentation systems.
openapi-designer
Design complete OpenAPI 3.1 specifications for RESTful APIs. Covers schemas, security, examples, webhooks, and documentation generation.