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/outlinedriven/outline-driven-development/doc-reviewnpx skills add OutlineDriven/outline-driven-development --skill doc-reviewgit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/doc-review)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/doc-review"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/doc-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.00060 | $0.07096 |
| Opus 5 | $0.00030 | $0.03548 |
| Sonnet 5 | $0.00012 | $0.01419 |
| Haiku 4.5 | $0.00006 | $0.00710 |
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 yesterday.
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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc review
Contract
| Field | Bound contract |
|---|---|
| Trigger | The user asks to review or critique a prose planning document (plan, spec, PRD, requirements, design doc, brainstorm) or invokes /doc-review [path]. |
| Authority | Reversible-local. The orchestrator may write at most one review-record file docs/reviews/<doc-slug>-review.md, and only when --record is requested. Dispatched reviewer subagents are read-only (no Write, no Edit, no files). The reviewed document is never edited, written, or committed. |
| Side effect | At most one local review-record file, only on --record; read-only subagent dispatch. No mutation of the reviewed document or any other tree path. Rollback: delete the single record file; nothing else was touched. |
| Done | Findings routed to safe-auto / gated-auto / manual / FYI tiers with verbatim evidence, zero writes to the reviewed document, and the terminal signal Review complete. |
Inputs
- A prose planning document path (requirements, plan, spec, PRD, design doc, or brainstorm). Optional: with no path, list
.mdcandidates from likely homes and let the user choose; never silently auto-pick. In headless mode a path is required. - Optional flags parsed from arguments (tokens starting with
mode:or--are flags, not paths):mode:headless(non-interactive: structured findings, no questions, no record unless--record);--record(persist one review-record file and stage only it). - The document's
origin:frontmatter value, or the literalnonewhen absent. Extracted once and passed to every reviewer.
Procedure
- Detect mode. Done when: one mode is fixed for the run.
Strip flag tokens from the arguments; use the remaining token as the document path. If mode:headless is present, run headless for the whole workflow: findings return as structured text, no blocking-question prompts, no interactive routing, Phase 5 returns immediately with Review complete. Otherwise run interactive mode.
What ships with it
14 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.
- agents/openai.yaml 177 B
- references/bulk-preview.md 7.0 KB
- references/findings-schema.json 4.2 KB
- references/open-questions-defer.md 3.8 KB
- references/personas/adversarial.md 4.5 KB
- references/personas/coherence.md 3.1 KB
- references/personas/feasibility.md 3.3 KB
- references/personas/product.md 3.9 KB
- references/personas/scope-guardian.md 3.4 KB
- references/personas/security.md 3.1 KB
- references/review-output-template.md 8.8 KB
- references/subagent-template.md 26 KB
- references/synthesis-and-presentation.md 26 KB
- references/walkthrough.md 9.7 KB
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.
- yesterday First seen · 298 lines · 60 tokens per session scan A a098d9a8e213
doc-review is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed today), licensed Apache-2.0. It adds 60 tokens to every session and 7,096 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-09-03.
Other skills, from other repositories
outlines
Guarantee valid JSON/XML/code structure during generation, use Pydantic models for type-safe outputs, support local models (Transformers, vLLM), and maximize inference speed with Outlines - dottxt.ai's structured generation library.
brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning, not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or…
doc-review
Use when the user asks to review or critique a prose planning document — a plan, spec, PRD, requirements doc, or design doc.
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
git-branchless
Use when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms and a publish gate. Not for plain-git workflows in repos without branchless; the skill stays inert there. Human-only.
setup-gitignore
Use when the user says set up gitignore, fix gitignore, or untracked files keep appearing. Writes or merges .gitignore under stable section anchors and proves reruns produce no diff. Not for remote, credential, publish, deploy, or irreversible changes.