docs-update

docs-update is a command for coding agents from C0ntr0lledCha0s/claude-code-plugin-automations. It costs 7 tokens per session (693 once invoked), scanned A, original, MIT.

A command that brings existing documentation in line with the current code. It compares functions, classes, exports, parameters, return values, and descriptions.

In plain words
What is it for?
Use it to update documentation for a specified file or to report needed changes without editing when using check-only mode.
Why use it?
It finds documentation that is missing, outdated, or inconsistent with the code, so developers do not have to check every detail manually.

Command

Part of the documents-manager plugin — 3 skills, 4 commands, 1 agent shipped together

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/c0ntr0lledcha0s/claude-code-plugin-automations/docs-update
Clone the repo
git clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations

Or install documents-manager, the plugin that ships this one along with the rest of its 3 skills, 4 commands, 1 agent.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/docs-update.svg)](https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/docs-update)
Your own site
<a href="https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/docs-update"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/docs-update.svg" alt="Measured on agentmods" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 693 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.

ModelPer sessionOnce invoked
Fable 5 $0.00007 $0.00693
Opus 5 $0.00003 $0.00347
Sonnet 5 $0.00001 $0.00139
Haiku 4.5 $0.00001 $0.00069

Measured 4d ago against content hash f6c43d1f64c0, 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 4d 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.

documents-manager/commands/docs-update.md · 116 lines

How it starts

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

Documentation Updater

Update documentation to match the current state of the code.

Target: $ARGUMENTS

Parsing Arguments

  1. File path: Required - the file to update documentation for
  2. --check-only: Optional - only report what needs updating, don't make changes

Update Process

Step 1: Analyze Current Code

  1. Read the target file
  2. Parse all functions, classes, and exports
  3. Extract:
    • Function signatures (parameters, return types)
    • Class structures (properties, methods)
    • Module exports

Step 2: Analyze Existing Documentation

  1. Find existing documentation for each item
  2. Extract documented:
    • Parameter names and types
    • Return values
    • Descriptions

Step 3: Compare and Identify Mismatches

  1. Missing Parameters: Params in code but not in docs
  2. Extra Parameters: Params in docs but not in code
  3. Type Mismatches: Different types in code vs docs
  4. Missing Documentation: Items with no docs
  5. Stale Descriptions: Descriptions that don't match behavior

Step 4: Generate Updates

For each mismatch:

  1. Generate corrected documentation
  2. Preserve existing good content
  3. Add placeholders for new items
  4. Mark items for human review if unclear

Step 5: Apply Changes (unless --check-only)

  1. Show diff of proposed changes
  2. Ask for confirmation
  3. Apply updates
  4. Report summary

Output Modes

Check-Only Mode (--check-only)

## Documentation Update Report

### Outdated Documentation Found

**file.js:functionName**
- Parameter `newParam` added but not documented
- Return type changed from `string` to `Promise<string>`

**file.js:className**
- Method `newMethod` added but not documented
- Property `oldProp` removed but still documented

### Summary
- 3 functions need updates
- 2 classes need updates
- 5 total documentation changes needed

Update Mode (default)

  1. Show proposed changes with diffs
  2. Ask for confirmation
  3. Apply changes
  4. Show summary of updates made

Read the full file on GitHub · 116 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. 4d ago First seen · 116 lines · 7 tokens per session scan A f6c43d1f64c0

Subscribe to this mod's changes

docs-update is a command published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 693 once invoked, about $0.0000 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.