A command that checks project documentation against recent Git changes, where Git records changes to the codebase. It can review README files, project instructions, extension documentation, dashboard API documentation, or all supported documentation.

Use it to review documentation after recent commits, limit the review to a selected area, preview possible updates, and update approved documentation.

It helps find instructions that no longer match the software after code changes.

docs-update — Command by Osmantic

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/osmantic/ods/docs-update

Clone the repo

git clone --depth 1 https://github.com/Osmantic/ODS

Made for: Claude Code.

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

When invoked 2,760 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.00000	$0.02760
Opus 5	$0.00000	$0.01380
Sonnet 5	$0.00000	$0.00552
Haiku 4.5	$0.00000	$0.00276

Measured yesterday against content hash 8deec5b2a496, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docs-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 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.

.claude/commands/docs-update.md · 337 lines

How it starts

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

ODS Documentation Review and Update

Review all project documentation against recent git changes with full project context. This command understands the installer architecture, extension system, GPU tier mapping, Docker compose layering, dashboard API, and dashboard UI.

Arguments

commits: Number of recent commits to analyze (default: 20)
--dry-run: Preview changes without applying them
--scope: Limit scope to specific docs (default: all)
- all - All documentation files
- readme - README.md only
- claude - CLAUDE.md only
- extensions - Extension-related docs only
- dashboard-api - Dashboard API README only

Philosophy: Ask Early, Ask Often

This skill should liberally use AskUserQuestion at decision points. Documentation changes are visible to the whole team and affect onboarding. Confirm scope and validate findings before modifying files.

Before analyzing — confirm which docs and how many commits to review
After generating the staleness report — let the user choose which docs to update
Before applying edits — present proposed changes for approval
When cross-doc inconsistencies are found — ask which doc is the source of truth

Documentation Files (In-Scope)

Doc File	Purpose	Scope Key
`README.md`	Main project documentation	readme
`CLAUDE.md`	Claude Code instructions	claude
`ods/README.md`	Core product documentation (if exists)	readme
`ods/extensions/services/dashboard-api/README.md`	Dashboard API documentation	dashboard-api
`ods/extensions/services/dashboard/README.md`	Dashboard UI documentation (if exists)	readme

Excluded Files

node_modules/, .venv/ - Dependencies
data/ - Runtime data
ods/token-spy/ - Dev tools
.git/ - Git internals

Step 1: Gather Git Context

1.1 Changed Files Analysis

Run git log --oneline -N --name-only --pretty=format: | sort -u | grep -v '^$' (N = commit count, default 20).

Read the full file on GitHub · 337 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.

yesterday First seen · 337 lines · 0 tokens per session scan A 8deec5b2a496

Subscribe to this mod's changes

docs-update is a command published in the GitHub repository Osmantic/ODS (5,145 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,760 tokens. 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-30.

Analytics and metrics Code review Git and workflow LLM ai-agents amd comfyui docker self-hosted

docs-update

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

ODS Documentation Review and Update

Arguments

Philosophy: Ask Early, Ask Often

Documentation Files (In-Scope)

Excluded Files

Step 1: Gather Git Context

1.1 Changed Files Analysis

What this file has done since we first saw it

Other commands, from other repositories

resume-workflow

start-development

finish-feature

text-to-3d

triage

domains