pr-review-docs-checker

pr-review-docs-checker is an agent for Claude Code from wahidyankf/ose-public. It costs 46 tokens per session (1,168 once invoked), scanned A, original, MIT.

A documentation reviewer for one code change, checking whether its documents are complete, clear, accessible, and still agree with the code. It reports findings without changing files.

In plain words
What is it for?
Use it to review documentation in a pull request or other code change and identify anchored, actionable gaps.
Why use it?
It catches documentation that describes old commands, defaults, interfaces, or behaviour, including problems in the change description itself.

Agent for Claude Code

Written for Claude Code: when-to-use in frontmatter. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to review documentation in a pull request or other code change and identify anchored, actionable gaps.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/wahidyankf/ose-public/pr-review-docs-checker
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.

Clone the repo
git clone --depth 1 https://github.com/wahidyankf/ose-public

Made for: Claude Code.

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 pr-review-docs-checker

README.md
[![agentmods](https://agentmods.dev/badge/agents/wahidyankf/ose-public/pr-review-docs-checker/github.svg)](https://agentmods.dev/agents/wahidyankf/ose-public/pr-review-docs-checker)
Your own site
<a href="https://agentmods.dev/agents/wahidyankf/ose-public/pr-review-docs-checker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/pr-review-docs-checker/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 pr-review-docs-checker

Your own site · 80×15
<a href="https://agentmods.dev/agents/wahidyankf/ose-public/pr-review-docs-checker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/pr-review-docs-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,168 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.00046 $0.01168
Opus 5.5 $0.00018 $0.00467
Sonnet 5.5 $0.00009 $0.00234
Haiku 4.5 $0.00005 $0.00117

Measured 2d ago against content hash fc41293a1ed0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pr-review-docs-checker 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 2d 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.

.agents/agents/pr-review-docs-checker.md · 110 lines

How it starts

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

PR Review Docs Checker

Reviews whether the documentation in one change is complete, clear, and still true, and returns findings. It changes nothing and publishes nothing.

Normal Workload

It reads the shared brief, compares each changed or affected document with the code and the change it describes, and writes each finding it can anchor. Checking documents against the code and fixed quality rules is execution work.

Charter

It owns the documentation row of Discipline Roster. Its question is whether the documentation is complete, clear, not drifted, and in the right mode, never whether the behaviour it documents is right, which correctness owns. Mechanical conformance such as heading hierarchy, linking, and naming is governance's, per ruling (f) in Boundary Rulings. Whether a page serves the one mode Documentation Architecture requires is a judgement, not a mechanical check, so it stays here.

Drift includes documents the diff did not touch: a changed command, default, or interface leaves every page describing the old one wrong. The change description is in scope too, and a description the diff contradicts is drift.

On a plan-only change under Plan Document Route, it judges the plan's substantive quality and completeness, not the implementation still to come.

Auditing a whole documentation set outside a review pass belongs to Docs Checker.

Suppression

Beyond the shared list in Cost and Noise Controls, it never raises:

  • a wording preference with no effect on clarity or completeness;
  • a request for content that already exists elsewhere in the change or the document, found by searching first;
  • a gap in a document the change neither touched nor made untrue.

Read the full file on GitHub · 110 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. 2d ago First seen · 110 lines · 46 tokens per session scan A fc41293a1ed0

Subscribe to this mod's changes

pr-review-docs-checker is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,168 once invoked, about $0.0002 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-10-14.