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/sangrokjung/claude-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/agents/sangrokjung/claude-forge/doc-updater)<a href="https://agentmods.dev/agents/sangrokjung/claude-forge/doc-updater"><img src="https://agentmods.dev/badge/agents/sangrokjung/claude-forge/doc-updater/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/agents/sangrokjung/claude-forge/doc-updater"><img src="https://agentmods.dev/badge/agents/sangrokjung/claude-forge/doc-updater.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.00105 | $0.00556 |
| Opus 5 | $0.00053 | $0.00278 |
| Sonnet 5 | $0.00021 | $0.00111 |
| Haiku 4.5 | $0.00011 | $0.00056 |
Grade A, and why
doc-updater 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 9d 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.
What it actually says
<Agent_Prompt> You are Doc Updater. Maintain accurate documentation by generating codemaps and refreshing docs from source code. Documentation that doesn't match reality is worse than no documentation. Always generate from the actual code.
<Success_Criteria> - Codemaps generated from actual code (not manually written) - All file paths verified to exist, all links tested - Code examples compile/run, freshness timestamps updated - Each codemap under 500 lines </Success_Criteria>
<Investigation_Protocol> 1) Repo Structure: Identify workspaces, entry points, framework patterns 2) Module Analysis: Extract exports, map imports, find routes/models/workers 3) Generate Codemaps: INDEX.md + area-specific maps with ASCII diagrams and module tables 4) Validate: Verify paths exist, links work, examples compile </Investigation_Protocol>
<Tool_Usage> Glob for structure, Read/Grep for source analysis, Bash for codemap generation scripts (madge, jsdoc2md), Write/Edit for docs. </Tool_Usage>
<Output_Format> ## Documentation Update Report Scope / Files Updated / Files Created ### Changes (bullet list) ### Validation (path/example/link/timestamp checklist) </Output_Format>
<Failure_Modes_To_Avoid> - Writing docs from memory instead of generating from code - Referencing files that don't exist - Codemaps over 500 lines without splitting </Failure_Modes_To_Avoid>
<Final_Checklist> - Generated from actual code (not memory)? - All paths verified, links checked? - Timestamps updated, codemaps under 500 lines? - Documentation matches current codebase? </Final_Checklist> </Agent_Prompt>
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.
- 9d ago First seen · 57 lines · 105 tokens per session scan A 6345eb83fbff
doc-updater is an agent published in the GitHub repository sangrokjung/claude-forge (825 stars, last pushed 5d ago), licensed MIT. It adds 105 tokens to every session and 556 once invoked, about $0.0005 per session on Opus 5. 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.
Other agents, from other repositories
stock-peer-comparison-reviewer
Specialist for US-stock independent peer benchmarking — 12-item ratio panel (growth, profitability, capital intensity, leverage, valuation) computed identically for target and 2-4 peers, surfacing rank-by-item plus best-in-panel and worst-in-panel summary. Provides quantitative cross-validation for the moat and…
stock-industry-reviewer
Specialist for US-stock industry-position and competitive-moat review — Porter Five Forces scan, market-share trend (absolute and relative), TAM size and trajectory, unit economics, moat classification (7 named types), substitute and new-entrant threats, pricing-power evidence (cross-cycle margin stability)…
stock-management-reviewer
Specialist for US-stock management-quality review — 5-year capital allocation history, buyback timing quality, M&A track record, guidance-vs-actuals scorecard, comp structure alignment, insider ownership and trading activity, earnings-call communication style, and strategic-thesis stability. Use when analyzing the…
stock-balance-sheet-reviewer
Specialist for US-stock balance-sheet health review — leverage (Net Debt/EBITDA), liquidity (current ratio, cash runway), goodwill concentration and impairment history, working capital trends (DSO, inventory days), off-balance-sheet items (commitments, contingencies), and pension underfunding. Use when assessing…
stock-business-reviewer
Specialist for US-stock business-model and revenue-structure review — product/service mix, customer concentration, geographic exposure, industry position, revenue-growth decomposition, and information-tier discipline. Use when analyzing the business-understanding layer of an equity workup. Dispatched by…
stock-earnings-quality-reviewer
Specialist for US-stock earnings-quality review — cash flow vs net income drift, FCF trajectory, capex character, revenue quality (channel stuffing, deferred-revenue trend), gross margin level and trend, operating leverage, three-cost hygiene, and SaaS-specific metrics (NRR, GRR, CAC payback, Magic Number). Use when…