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 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/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/outlinedriven/outline-driven-development/doc-review"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/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.00041 | $0.07092 |
| Opus 5.5 | $0.00016 | $0.02837 |
| Sonnet 5.5 | $0.00008 | $0.01418 |
| Haiku 4.5 | $0.00004 | $0.00709 |
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 — 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: writes at most one review-record file docs/reviews/<doc-slug>-review.md, and only when --record is requested; rollback is deleting that file. No remote mutation. Dispatched reviewer subagents are read-only; 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, step 6 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.4 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.3 KB
- references/personas-security.md 3.1 KB
- references/review-output-template.md 8.9 KB
- references/subagent-template.md 26 KB
- references/synthesis-and-presentation.md 26 KB
- references/walkthrough.md 9.6 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.
- 1mo ago Changed · -19 tokens per session 9ae2fe961502
- 1mo ago 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 (53 stars, last pushed 22d ago), licensed Apache-2.0. It adds 41 tokens to every session and 7,092 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-09-03.
Other skills, from other repositories
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
duet
Use when the user invokes /duet, says "pair with me", or faces aesthetic, architectural, or irreversible decisions.
goal-prompt-drafting
Use when asked to draft copy-ready /goal objectives for long-running agents; returns one normalized one-line objective with measurable end state, grounded proof, easy-out invariants, a stop clause, and a Missing list. Not for source or remote-system changes.
handoff-prompt
Use when the user asks for a handoff, delegation, or clipboard-ready prompt for another agent: a standalone path-free prompt copied to the clipboard, confirmed by title. Not for session-snapshot briefs — use handoff; never remote, credential, publish, deploy, or irreversible.
publish-branch
Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.
drill
Use when a concept needs practising rather than explaining: run a scaffolded exercise from worked example to independent problem, quiz the learner, run spaced recall over what they cleared, or probe for the gaps blocking what they want next. For explanation, use explain-concept; for an end-to-end build, use capstone.