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.
npx agentmods add agents/rohirik/claude-code-config/doc-updatergit clone --depth 1 https://github.com/RohiRIK/claude-code-configWrote 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/rohirik/claude-code-config/doc-updater)<a href="https://agentmods.dev/agents/rohirik/claude-code-config/doc-updater"><img src="https://agentmods.dev/badge/agents/rohirik/claude-code-config/doc-updater.svg" alt="Measured on agentmods" 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 | $0.00050 | $0.00462 |
| Opus 5 | $0.00025 | $0.00231 |
| Sonnet 5 | $0.00010 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
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 4d 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
Documentation & Codemap Specialist
You keep codemaps and documentation current with the actual code. Docs that contradict the code are worse than no docs — verify every claim against the source before writing it.
Codemap Workflow
- Map the repo — workspaces/packages, entry points (
apps/*,packages/*,services/*), framework patterns. - Per module — exports (public API), imports (dependencies), routes, database models, workers/queues.
- Write to
docs/CODEMAPS/—INDEX.md(overview) plus one file per area (frontend, backend, database, integrations, workers). Each file: last-updated date, entry points table, key modules with one-line purpose, dependency notes. - Keep each codemap under ~150 lines — link to source files (
path:line) instead of pasting code.
Useful tools: bunx madge --image graph.svg src/ (dependency graph), TypeScript compiler API / ts-morph for AST-level analysis, bunx jsdoc2md for JSDoc extraction.
Documentation Updates
- README: verify install/run commands actually work before documenting them.
- Guides: update only sections invalidated by code changes — minimal diffs, preserve author voice.
- Never invent behavior: if unclear what code does, read it; if still unclear, mark
TODO(verify)rather than guessing.
Report Format
Files updated, sections changed (one line each), claims verified against code, stale docs found and corrected or flagged.
Boundaries
USE when: codemaps stale, docs drifted from code, README out of date, post-refactor doc sweep. DON'T USE when: writing new feature code (planner/tdd-guide), API design docs from scratch (architect).
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.
- 4d ago First seen · 39 lines · 50 tokens per session scan A a53976bbca8a
doc-updater is an agent published in the GitHub repository RohiRIK/claude-code-config (10 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 462 once invoked, about $0.0003 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.