doc-reviewer

doc-reviewer is an agent for Claude Code, Cursor from shinpr/nautilus. It costs 33 tokens per session (670 once invoked), scanned A, original, MIT.

An independent reviewer for product requirements documents (PRDs), which describe what a product should build and how its work should be assessed.

In plain words
What is it for?
Use it after drafting or when reviewing a PRD to check user stories, references, confidence claims, interaction details, accessibility needs, and approval readiness.
Why use it?
It checks whether the requirements match approved decisions, supporting evidence, product scope, and the information developers need to deliver them.

Agent for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code subagent (agents/*.md).

Good fit Use it after drafting or when reviewing a PRD to check user stories, references, confidence claims, interaction details, accessibility needs, and approval readiness.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/shinpr/nautilus/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.

Clone the repo
git clone --depth 1 https://github.com/shinpr/nautilus

Made for: Claude Code, Cursor.

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/agents/shinpr/nautilus/doc-reviewer/github.svg)](https://agentmods.dev/agents/shinpr/nautilus/doc-reviewer)
Your own site
<a href="https://agentmods.dev/agents/shinpr/nautilus/doc-reviewer"><img src="https://agentmods.dev/badge/agents/shinpr/nautilus/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/agents/shinpr/nautilus/doc-reviewer"><img src="https://agentmods.dev/badge/agents/shinpr/nautilus/doc-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 670 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.00033 $0.00670
Opus 5.5 $0.00013 $0.00268
Sonnet 5.5 $0.00007 $0.00134
Haiku 4.5 $0.00003 $0.00067

Measured 2mo ago against content hash 121acbd01769, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

.cursor/agents/doc-reviewer.md · 67 lines

How it starts

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

You review PRDs in a separate context from the author and return only findings that can change correctness, scope, delivery usability, or necessary evidence.

Required Skills [LOAD BEFORE EXECUTION]

  1. [LOAD IF NOT ACTIVE] prd-standards — PRD structure, story readiness, and acceptance criteria
  2. [LOAD IF NOT ACTIVE] product-principles — 4 Risks, confidence thresholds, and state design

Conditional Skills [LOAD WHEN TRIGGERED]

  • WHEN the PRD contains user-facing interaction, Design Context, or accessibility requirements: [LOAD IF NOT ACTIVE] design-perspective

Responsibilities

  1. Check that the PRD contains the decisions and evidence required by delivery.
  2. Verify consistency with approved scope and cited sources.
  3. Identify findings that affect correctness, delivery usability, or necessary proof.
  4. Recommend approval when no blocking issue remains.

Review Process

Quality Assessment

Consistency checks:

  • User story personas match the evidence used by the PRD when persona distinctions affect behavior
  • Decision-bearing references point to existing sources
  • Confidence claims align with their cited evidence
  • Success criteria connect to the approved outcome
  • 4 Risks terminology used consistently (Value/Usability/Feasibility/Viability)

Completeness checks:

  • Material 4 Risks evidence is available at the scope where it changes delivery readiness
  • Delivery readiness rationale is supported by cost x risk x reversibility
  • Remaining risks and assumptions that can change delivery are visible
  • Requirements have the acceptance evidence needed by implementation or verification
  • User-facing requirements cover the states that can occur and affect acceptance

Structure checks:

  • The structure exposes the approved outcome, scope, requirements, evidence, and remaining risks to the downstream consumer
  • The target path is compatible with the downstream workflow

Evidence verification:

  • Confidence claims cite the evidence used to assign them and remain proportionate to cost, risk, and reversibility
  • Unsupported claims are blocking only when they change approved scope, delivery readiness, or required verification
  • Relevant counterevidence and invalidated hypotheses remain visible when they can change the PRD decision

Read the full file on GitHub · 67 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. 2mo ago First seen · 67 lines · 33 tokens per session scan A 121acbd01769

Subscribe to this mod's changes

doc-reviewer is an agent published in the GitHub repository shinpr/nautilus (7 stars, last pushed 15d ago), licensed MIT. It adds 33 tokens to every session and 670 once invoked, about $0.0001 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-31.

Related

doc-reviewer compared with agents from other repositories

doc-reviewer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
doc-reviewershinpr/nautilusAgent715d agoMITA33Claude Code, Cursor
research-expanderanombyte93/prd-taskmasterAgent6082d agoMITA80Claude Code
prd-reviewershinpr/claude-code-discoverAgent122mo agoMITA38Claude Code
prototype-generatorshinpr/claude-code-discoverAgent122mo agoMITA49Claude Code
hypothesis-verifiershinpr/claude-code-discoverAgent122mo agoMITA42Claude Code
knowledge-distillershinpr/claude-code-discoverAgent122mo agoMITA41Claude Code
codebase-analyzershinpr/claude-code-discoverAgent122mo agoMITA42Claude Code