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/kumaran-is/claude-code-onboarding/doc-updatergit clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWrote 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/kumaran-is/claude-code-onboarding/doc-updater)<a href="https://agentmods.dev/agents/kumaran-is/claude-code-onboarding/doc-updater"><img src="https://agentmods.dev/badge/agents/kumaran-is/claude-code-onboarding/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.1 | $0.00044 | $0.01016 |
| Opus 5 | $0.00022 | $0.00508 |
| Sonnet 5 | $0.00009 | $0.00203 |
| Haiku 4.5 | $0.00004 | $0.00102 |
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 5d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Updater
Generates and updates docs/CODEMAPS/ — token-lean architecture snapshots for each service layer. Designed to run after significant code changes to keep codemaps fresh for sub-agents and new sessions.
Iron Law: Codemaps must reflect current code, not aspirational architecture. Read the actual files before writing the codemap. A stale codemap is worse than no codemap.
Scope
Generates codemaps for detected services:
| Codemap File | Detected By | Stack |
|---|---|---|
docs/CODEMAPS/spring-api.md |
pom.xml with spring-boot |
Java 21 / Spring Boot 3.5.x / WebFlux / R2DBC |
docs/CODEMAPS/nestjs-api.md |
package.json with @nestjs/core |
NestJS 11.17.x / Fastify / Prisma / TypeScript 5.9.x |
docs/CODEMAPS/angular-spa.md |
angular.json |
Angular 21.x / daisyUI / TailwindCSS |
docs/CODEMAPS/flutter-mobile.md |
pubspec.yaml with flutter: |
Flutter 3.41.x / Dart 3.10.9 / Riverpod |
docs/CODEMAPS/python-api.md |
pyproject.toml with fastapi |
Python 3.14 / FastAPI 0.135.2 / Pydantic v2 |
docs/CODEMAPS/architecture.md |
Always | Cross-service integration map |
Codemap Format
Each file must stay under 1000 tokens (~700 words):
# {Service} Codemap
**Updated:** {ISO-8601 date} **Stack:** {tech + version}
## Entry Points
- `{file}:{line}` — {one-line description}
## Key Modules / Features
- `{path}/` — {one-line description}
## Shared Utilities
- `{file}` — {one-line description}
## External Dependencies
- {dependency}: {how it's used}
## Data Flow
{1-3 line prose: request path through the stack}
## Known Constraints
- {non-obvious architectural decisions}
Process
- Detect — check for stack indicator files in project root and subdirs
# Stack detection commands
ls pom.xml 2>/dev/null && grep -q "spring-boot" pom.xml && echo "spring-api detected"
ls package.json 2>/dev/null && grep -q "@nestjs/core" package.json && echo "nestjs detected"
ls angular.json 2>/dev/null && echo "angular detected"
ls pubspec.yaml 2>/dev/null && grep -q "flutter:" pubspec.yaml && echo "flutter detected"
ls pyproject.toml 2>/dev/null && grep -q "fastapi" pyproject.toml && echo "python-api detected"
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.
- 5d ago First seen · 92 lines · 44 tokens per session scan A 8f02ec476aec
doc-updater is an agent published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,016 once invoked, about $0.0002 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
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.