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.
git clone --depth 1 https://github.com/XRenSiu/claude-code-forgeWrote 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.
[](https://agentmods.dev/commands/xrensiu/claude-code-forge/update-docs)<a href="https://agentmods.dev/commands/xrensiu/claude-code-forge/update-docs"><img src="https://agentmods.dev/badge/commands/xrensiu/claude-code-forge/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.
<a href="https://agentmods.dev/commands/xrensiu/claude-code-forge/update-docs"><img src="https://agentmods.dev/badge/commands/xrensiu/claude-code-forge/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00678 |
| Opus 5.5 | $0.00000 | $0.00271 |
| Sonnet 5.5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/update-docs Command
Synchronize project documentation with code changes.
Usage
/update-docs [scope] [options]
Arguments
| Argument | Required | Default | Description |
|---|---|---|---|
| scope | No | all | What to update: readme, api, codemap, changelog, all |
Options
| Option | Description |
|---|---|
| --path | Specific code path to analyze |
| --since | Generate changelog since commit/tag |
| --format | Output format (markdown/openapi/jsdoc) |
| --verify | Verify existing docs without updating |
| --diff | Show what would change without applying |
Examples
# Update all documentation
/update-docs
# Update only API documentation
/update-docs api
# Update changelog since last release
/update-docs changelog --since v1.0.0
# Generate codemap for specific directory
/update-docs codemap --path src/api
# Verify docs are in sync (CI use)
/update-docs --verify
# Preview changes without applying
/update-docs readme --diff
Scope Details
readme
- Project description
- Installation instructions
- Quick start guide
- Environment variables
- Dependencies
api
- Route definitions
- Request/response schemas
- Authentication requirements
- Status codes
- Examples
codemap
- Directory structure
- Module purposes
- Key file descriptions
- Dependency graph
changelog
- New features (Added)
- Modifications (Changed)
- Bug fixes (Fixed)
- Security patches (Security)
- Deprecations (Deprecated)
- Removals (Removed)
Workflow
-
Detect Changes
- Compare code with existing docs
- Identify outdated sections
- Find undocumented APIs
-
Generate Updates
- Extract info from code
- Apply documentation templates
- Maintain consistent style
-
Verify Accuracy
- Test code examples
- Validate links
- Cross-reference types
-
Apply Changes
- Update doc files
- Commit with descriptive message
Agent Invocation
This command invokes the doc-updater agent:
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.
- 1mo ago First seen · 142 lines · 0 tokens per session scan A 5534ea158524
update-docs is a command published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 678 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-05.
Other commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.