update-docs

A workflow for keeping project documentation accurate after code changes. It reviews recent changes and updates the README, development notes, component guides and inline comments.

In plain words
What is it for?
Use it after adding features, changing services or APIs, modifying data structures, introducing integrations or changing environment variables.
Why use it?
It prevents setup instructions, API details, examples and configuration notes from becoming out of date.

Command

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/cassler/awesome-claude-code-setup/update-docs
Clone the repo
git clone --depth 1 https://github.com/cassler/awesome-claude-code-setup
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 237 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.00000 $0.00237
Opus 5 $0.00000 $0.00118
Sonnet 5 $0.00000 $0.00047
Haiku 4.5 $0.00000 $0.00024

Measured 2d ago against content hash 5778a678fd31, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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 · 36 lines

What it actually says

Update Documentation

Please update the project documentation to reflect recent changes:

  1. Identify recent changes - Review git history and modified files to understand what has changed

  2. Update README.md - Ensure the main README reflects:

    • Any new features or capabilities
    • Updated setup instructions if needed
    • New environment variables
    • Changed ports or services
  3. Update CLAUDE.md - Add any new:

    • Architectural decisions
    • Development patterns discovered
    • Common issues and solutions
    • Testing insights
  4. Check component docs - Update documentation for:

    • New APIs or endpoints
    • Modified workflows
    • Changed data schemas
    • New integrations
  5. Update inline documentation:

    • JSDoc/TSDoc comments for new functions
    • Configuration file comments
    • Environment variable descriptions
  6. Verify accuracy - Ensure all:

    • Code examples still work
    • Commands are up to date
    • Links are not broken
    • Version numbers are current

Focus on clarity and helping future developers (including yourself) understand the system quickly.

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. 2d ago First seen · 36 lines · 0 tokens per session scan A 5778a678fd31

Subscribe to this mod's changes

update-docs is a command published in the GitHub repository cassler/awesome-claude-code-setup (267 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 237 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.