EGC: Command for Claude Code

.opencode/commands/update-docs.md

update-docs is a command for Claude Code, OpenCode from Fmarzochi/EGC. It costs 5 tokens per session (312 once invoked), scanned A, a copy of update-docs, Apache-2.0.

A command that updates documentation to match recent code changes, such as installation guides, API references, and examples.

In plain words
What is it for?
Finding changed files, updating READMEs and guides, documenting public APIs, improving code comments, and checking examples and links.
Why use it?
It prevents documentation from becoming inaccurate or leaving out newly changed behavior.

Command for Claude CodeOpenCode

Written for Claude Code and OpenCode: $ARGUMENTS substitution, but also installed under .opencode/. Also seen: agent in frontmatter.

This is Fmarzochi/EGC's own configuration. It tells Claude Code and OpenCode how to work on EGC itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything EGC configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Fmarzochi/EGC. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Fmarzochi/EGC/main/.opencode/commands/update-docs.md
Clone the repo
git clone --depth 1 https://github.com/Fmarzochi/EGC

Made for: Claude Code, OpenCode.

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/fmarzochi/egc/update-docs/github.svg)](https://agentmods.dev/commands/fmarzochi/egc/update-docs)
Your own site
<a href="https://agentmods.dev/commands/fmarzochi/egc/update-docs"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/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/fmarzochi/egc/update-docs"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/update-docs.svg" alt="Reviewed on agentmods" width="80" 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 312 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 92% copy Near-identical to another mod 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.00005 $0.00312
Opus 5.5 $0.00002 $0.00125
Sonnet 5.5 $0.00001 $0.00062
Haiku 4.5 $0.00001 $0.00031

Measured 1mo ago against content hash ac213bcd2f73, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

Origin

This is a copy

92% identical to update-docs — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

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

What it actually says

Update Docs Command

Update documentation to reflect recent changes: $ARGUMENTS

Your Task

  1. Identify changed code - git diff --name-only
  2. Find related docs - README, API docs, guides
  3. Update documentation - Keep in sync with code
  4. Verify accuracy - Docs match implementation

Documentation Types

README.md

  • Installation instructions
  • Quick start guide
  • Feature overview
  • Configuration options

API Documentation

  • Endpoint descriptions
  • Request/response formats
  • Authentication details
  • Error codes

Code Comments

  • JSDoc for public APIs
  • Complex logic explanations
  • TODO/FIXME cleanup

Guides

  • How-to tutorials
  • Architecture decisions (ADRs)
  • Troubleshooting guides

Update Checklist

  • README reflects current features
  • API docs match endpoints
  • JSDoc updated for changed functions
  • Examples are working
  • Links are valid
  • Version numbers updated

Documentation Quality

Good Documentation

  • Accurate and up-to-date
  • Clear and concise
  • Has working examples
  • Covers edge cases

Avoid

  • Outdated information
  • Missing parameters
  • Broken examples
  • Ambiguous language

IMPORTANT: Documentation should be updated alongside code changes, not as an afterthought.

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. 1mo ago First seen · 68 lines · 5 tokens per session scan A ac213bcd2f73

Subscribe to this mod's changes

update-docs is a command published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed today), licensed Apache-2.0. It adds 5 tokens to every session and 312 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to update-docs, differing in 2 lines, and is treated as a copy.