A command for updating project documentation after code changes. It checks changed files, finds related documentation, and brings examples and API descriptions up to date.

Use it after changing features, endpoints, configuration, public functions, or architecture documentation.

It reduces the risk that README files, guides, API references, or code comments describe behavior the code no longer has.

update-docs — Command for coding agents by affaan-m: A command for updating project documentation after code changes.

About the project

ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.

affaan-m/ECC · 248,541 stars · on GitHub · ecc.tools

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/affaan-m/ecc/update-docs

Clone the repo

git clone --depth 1 https://github.com/affaan-m/ECC

Or install ecc, the plugin that ships this one along with the rest of its 70 skills, 56 commands, 68 agents, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/affaan-m/ecc/update-docs.svg)](https://agentmods.dev/commands/affaan-m/ecc/update-docs)

Your own site

<a href="https://agentmods.dev/commands/affaan-m/ecc/update-docs"><img src="https://agentmods.dev/badge/commands/affaan-m/ecc/update-docs.svg" alt="Measured on agentmods" height="20"></a>

Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 309 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.

Model	Per session	Once invoked
Fable 5.1	$0.00005	$0.00309
Opus 5	$0.00003	$0.00154
Sonnet 5	$0.00001	$0.00062
Haiku 4.5	$0.00001	$0.00031

Measured yesterday against content hash 2a036d2ed5b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, 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 yesterday.

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.

Origin

Copies of this mod

7 near-identical copies found in the catalogue:

update-docs — 100% identical, 0 lines differ
update-docs — 100% identical, 0 lines differ
update-docs — 100% identical, 0 lines differ
update-docs — 100% identical, 0 lines differ
update-docs — 92% identical, 2 lines differ
update-docs — 91% identical, 2 lines differ
update-docs — 89% identical, 2 lines differ

.opencode/commands/update-docs.md · 68 lines

What it actually says