A command that checks project documentation against a specification, which is a written description of planned changes.

Use it to review Markdown files, identify outdated sections, suggest replacement wording, and draft documentation for new features.

It finds documentation that describes removed or changed behavior, as well as new information that is missing.

doc-update — Command for Claude Code by dork-labs: A command that checks project documentation against a specification…

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.

agentmods

npx agentmods add commands/dork-labs/dorkos/doc-update

Clone the repo

git clone --depth 1 https://github.com/dork-labs/dorkos

Made for: Claude Code.

Or install flow, the plugin that ships this one along with the rest of its 17 skills, 37 commands, 5 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/dork-labs/dorkos/doc-update.svg)](https://agentmods.dev/commands/dork-labs/dorkos/doc-update)

Your own site

<a href="https://agentmods.dev/commands/dork-labs/dorkos/doc-update"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/doc-update.svg" alt="Measured on agentmods" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 408 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00010	$0.00408
Opus 5	$0.00005	$0.00204
Sonnet 5	$0.00002	$0.00082
Haiku 4.5	$0.00001	$0.00041

Measured 3d ago against content hash f398c4f6569b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

doc-update 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 3d 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.

.claude/commands/spec/doc-update.md · 41 lines

What it actually says

Documentation Update Review Based on Spec

Review all documentation for updates needed because of the specification at $ARGUMENTS.

Step 1: Read the Specification

Read the spec and identify what it deprecates/removes, what it changes, and what it adds — these are the three lenses every doc gets reviewed through.

Step 2: Gather Documentation Files

Glob root-level *.md and contributing/*.md.

Step 3: Review Each Doc Against the Spec

For a handful of docs, review them inline. For a larger set, dispatch general-purpose agents in parallel (batch several docs per agent; launch all agents in a single message). Give each agent a 3-5 sentence summary of the spec's key changes plus its doc list, and have it report per file:

Deprecated content — sections documenting functionality the spec removes; quote the doc text, cite the spec section, and mark severity: CRITICAL (following the doc would break) vs WARNING (merely outdated)
Content requiring updates — quote the current text, explain what changed per the spec, suggest updated wording
Missing content — new functionality that belongs in this doc, with suggested placement and draft text
Or simply: "No updates required."

Step 4: Consolidate and Act

Aggregate into a per-file summary table with priority counts: P0 deprecated-but-documented, P1 misleading, P2 missing new features, P3 minor.
Present detailed findings ordered by priority across all files.
Recommend which files need attention first and the rough effort for each.
Ask whether to implement the suggested updates now.

Usage

/spec:doc-update specs/<slug>/02-specification.md

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.

3d ago First seen · 41 lines · 10 tokens per session scan A f398c4f6569b

Subscribe to this mod's changes

doc-update is a command published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 408 once invoked, about $0.0001 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-08-31.

Autonomous Agents Code review Planning Writing and docs agent-sdk ai-agents anthropic claude claude-code workflow

doc-update