update-docs

A documentation-update command that builds contributor and operations documents from project configuration files. It uses package.json for scripts and .env.example for environment variables.

In plain words
What is it for?
Use it to generate development workflows, setup instructions, test steps, deployment and rollback procedures, monitoring guidance, troubleshooting notes, and script references.
Why use it?
It removes repetitive manual work and keeps key documentation tied to the project's declared settings. It also identifies documents that have not been changed for more than 90 days for review.

Command for Claude Code

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/cfrs2005/claude-init/update-docs
Clone the repo
git clone --depth 1 https://github.com/cfrs2005/claude-init

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 216 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.00216
Opus 5 $0.00000 $0.00108
Sonnet 5 $0.00000 $0.00043
Haiku 4.5 $0.00000 $0.00022

Measured 2d ago against content hash 85642a10f3ef, 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.

templates/.claude/commands/update-docs.md · 32 lines

What it actually says

更新文档 (Update Documentation)

从单一事实来源同步文档:

  1. 读取 package.jsonscripts 部分

    • 生成脚本参考表
    • 包含注释中的描述
  2. 读取 .env.example

    • 提取所有环境变量
    • 记录用途和格式
  3. 生成 docs/CONTRIB.md 包含:

    • 开发工作流
    • 可用脚本
    • 环境设置
    • 测试流程
  4. 生成 docs/RUNBOOK.md 包含:

    • 部署流程
    • 监控和报警
    • 常见问题与修复
    • 回滚流程
  5. 识别过时文档:

    • 查找 90 天以上未修改的文档
    • 列出供人工审查
  6. 显示差异摘要

单一事实来源:package.json.env.example

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 · 32 lines · 0 tokens per session scan A 85642a10f3ef

Subscribe to this mod's changes

update-docs is a command published in the GitHub repository cfrs2005/claude-init (1,364 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 216 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.