update-docs

update-docs is a command for Claude Code from travisjneuman/.claude. It costs 0 tokens per session (225 once invoked), scanned A, original, MIT.

A command that checks which project files changed and updates the documentation connected to those files.

In plain words
What is it for?
Use it after modifying skills, commands, agents, hooks, settings, plugins, or project guidance files.
Why use it?
It helps keep indexes, guides, changelogs, and other documentation consistent with code and configuration changes.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Good fit Use it after modifying skills, commands, agents, hooks, settings, plugins, or project guidance files.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/travisjneuman/.claude/update-docs
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.

Clone the repo
git clone --depth 1 https://github.com/travisjneuman/.claude

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/travisjneuman/.claude/update-docs/github.svg)](https://agentmods.dev/commands/travisjneuman/.claude/update-docs)
Your own site
<a href="https://agentmods.dev/commands/travisjneuman/.claude/update-docs"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/update-docs/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.

agentmods 80×15 button for update-docs

Your own site · 80×15
<a href="https://agentmods.dev/commands/travisjneuman/.claude/update-docs"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 225 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00225
Opus 5 $0.00000 $0.00112
Sonnet 5 $0.00000 $0.00045
Haiku 4.5 $0.00000 $0.00022

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

Security

Grade A, and why

update-docs 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 5d 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.

commands/update-docs.md · 23 lines

What it actually says

Update Documentation

Scan for recently modified files and update corresponding documentation.

Instructions

  1. Check which files were modified in this session using git diff --name-only and git diff --cached --name-only
  2. For each modified area, update the corresponding docs:
Modified Area Update
skills/ Regenerate skills/MASTER_INDEX.md — run bash ~/.claude/scripts/regenerate-index.sh
commands/ Verify command appears in skill listings
agents/ Update agents/README.md
hooks/ or settings.json Update docs/reference/tooling/ docs as needed
CLAUDE.md Verify satellite files are consistent
plugins/ Update docs/MARKETPLACE-GUIDE.md if plugin list changed
  1. Update cache/changelog.md with a summary of changes made
  2. Commit documentation updates together with the changes they describe

If arguments provided, focus on: $ARGUMENTS

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. 5d ago First seen · 23 lines · 0 tokens per session scan A ab9085e89ed9

Subscribe to this mod's changes

update-docs is a command published in the GitHub repository travisjneuman/.claude (96 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 225 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-09-03.