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 validatedpatterns/docs --skill doc-reviewgit clone --depth 1 https://github.com/validatedpatterns/docsWrote 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/validatedpatterns/docs/doc-review)<a href="https://agentmods.dev/skills/validatedpatterns/docs/doc-review"><img src="https://agentmods.dev/badge/skills/validatedpatterns/docs/doc-review/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/validatedpatterns/docs/doc-review"><img src="https://agentmods.dev/badge/skills/validatedpatterns/docs/doc-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00123 | $0.01800 |
| Opus 5.5 | $0.00049 | $0.00720 |
| Sonnet 5.5 | $0.00025 | $0.00360 |
| Haiku 4.5 | $0.00012 | $0.00180 |
Grade A, and why
doc-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 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review the documentation file(s) at $ARGUMENTS for compliance with the Red Hat/IBM Style Guide. Follow the workflow below precisely.
Step 1: Resolve targets
- If
$ARGUMENTSis empty, ask the user which file(s) or directory to review. - If
$ARGUMENTSis a directory, recursively glob for all*.adoc,*.md, and*.markdownfiles. - If
$ARGUMENTSis a file, use it directly. - If no matching files are found, inform the user and stop.
Step 2: Detect format and scan for likely violations (two-pass strategy)
For each file, detect the format by extension:
| Extension | Format |
|---|---|
.adoc |
AsciiDoc |
.md, .markdown |
Markdown |
Pass 1: Quick scan and guide selection
Read the file and scan for signals that indicate which rules are likely violated. Then load only the guides that are relevant, rather than all 24. This keeps reviews efficient without sacrificing coverage.
Always load these high-impact guides first (they catch the most common issues):
| Priority | Guide file | Topic | Load when you see... |
|---|---|---|---|
| P1 | guides/minimalism.md |
Conciseness, scannability, removing fluff | Long paragraphs, "in order to", "this section describes", filler adverbs |
| P2 | guides/passive-voice.md |
Prefer active voice | "is/are/was/were/been + past participle", "can be", "should be" |
| P3 | guides/avoid-these-words.md |
Full banned words table | Any uncertain word choice |
| P4 | guides/capitalization.md |
Sentence-style capitalization | Title-case headings |
| P5 | guides/titles-and-headings.md |
Gerunds for procedures, nouns for concepts | Procedural headings that don't start with a gerund |
| P6 | guides/contractions.md |
Avoid contractions | Apostrophes in words (don't, won't, it's, you'll) |
| P7 | guides/conscious-language.md |
Inclusive terminology | whitelist, blacklist, master, slave, sanity |
| P8 | guides/anthropomorphism.md |
No human traits for products | "system knows", "tries to", "smart enough" |
What ships with it
24 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.
- guides/anthropomorphism.md 943 B
- guides/asciidoc-specific.md 5.8 KB
- guides/avoid-these-words.md 5.2 KB
- guides/capitalization.md 663 B
- guides/colons-and-semicolons.md 1.7 KB
- guides/command-line.md 1.4 KB
- guides/commas-restrictive-nonrestrictive.md 1.2 KB
- guides/conscious-language.md 1.4 KB
- guides/contractions.md 747 B
- guides/future-tense.md 1001 B
- guides/incomplete-sentences.md 630 B
- guides/inline-links.md 916 B
- guides/markdown-specific.md 4.0 KB
- guides/minimalism.md 4.4 KB
- guides/optional-and-conditional-steps.md 1.0 KB
- guides/parallelism.md 985 B
- guides/passive-voice.md 941 B
- guides/phrasal-verbs.md 936 B
- guides/possessives-and-apostrophes.md 803 B
- guides/screen-captures.md 718 B
- guides/single-step-procedures.md 617 B
- guides/titles-and-headings.md 1.3 KB
- guides/ui-elements.md 1.6 KB
- guides/unordered-lists.md 578 B
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 · 130 lines · 123 tokens per session scan A 1d6072b222d6
doc-review is a skill published in the GitHub repository validatedpatterns/docs (20 stars, last pushed 2d ago), licensed Apache-2.0. It adds 123 tokens to every session and 1,800 once invoked, about $0.0005 per session on Opus 5.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-30.
Other skills, from other repositories
keep-the-why
In a project with a .keep-the-why, or when asked about Keep the Why or to set it up - extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup and maintainer interviews. Not for what changed (see Keep a Changelog) - only why.…
nextjs-supabase-vercel
Set up the current empty folder with the AI App Starter, so the agent builds a Next.js, Supabase and Vercel app with the owner step by step, from idea to launch.
sw-do
Work a SpecWeave increment task by task - claim, implement inside its Files, test, commit, done with evidence - alone, unattended or in lanes, then close. Use for "implement", "continue", "auto".
review
Adversarial review of an increment before it ships, by a fresh context or another model family; every finding cites path:line and is re-verified. Use for "review", "qa", "critique this".
pre-modification-check
Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core modules, public APIs, or files the user did not explicitly identify.
summarize
A guide for turning conversations, logs, documents, or investigation notes into short, action-oriented summaries. It requires conclusions to be tied to available evidence and distinguishes confirmed facts from items still needing confirmation.