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 commands/c0ntr0lledcha0s/claude-code-plugin-automations/docs-updategit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWrote 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/commands/c0ntr0lledcha0s/claude-code-plugin-automations/docs-update)<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>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.00007 | $0.00693 |
| Opus 5 | $0.00003 | $0.00347 |
| Sonnet 5 | $0.00001 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
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.
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
- File path: Required - the file to update documentation for
- --check-only: Optional - only report what needs updating, don't make changes
Update Process
Step 1: Analyze Current Code
- Read the target file
- Parse all functions, classes, and exports
- Extract:
- Function signatures (parameters, return types)
- Class structures (properties, methods)
- Module exports
Step 2: Analyze Existing Documentation
- Find existing documentation for each item
- Extract documented:
- Parameter names and types
- Return values
- Descriptions
Step 3: Compare and Identify Mismatches
- Missing Parameters: Params in code but not in docs
- Extra Parameters: Params in docs but not in code
- Type Mismatches: Different types in code vs docs
- Missing Documentation: Items with no docs
- Stale Descriptions: Descriptions that don't match behavior
Step 4: Generate Updates
For each mismatch:
- Generate corrected documentation
- Preserve existing good content
- Add placeholders for new items
- Mark items for human review if unclear
Step 5: Apply Changes (unless --check-only)
- Show diff of proposed changes
- Ask for confirmation
- Apply updates
- 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)
- Show proposed changes with diffs
- Ask for confirmation
- Apply changes
- Show summary of updates made
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.
- 4d ago First seen · 116 lines · 7 tokens per session scan A f6c43d1f64c0
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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.