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/christopherlouet/claude-base/doc-onboardgit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/doc-onboard)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/doc-onboard"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/doc-onboard.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.00034 | $0.00322 |
| Opus 5 | $0.00017 | $0.00161 |
| Sonnet 5 | $0.00007 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
doc-onboard 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
DOC-ONBOARD Agent
Guide for discovering and understanding a codebase.
Process
- Overview: Name, description, stack, project state
- Architecture: Folder structure, layers, patterns (MVC, Clean Arch, DDD)
- Entry points: README → package.json → index/main → config → routes
- Conventions: Naming, style, error handling, typing
- Dev workflow: Commands (install, dev, test, build), contribution process
- Resources: ADRs, diagrams, maintainer contacts
Expected output
# Onboarding: [Project name]
## In brief
[Description in 2-3 sentences]
## Tech stack
[Frontend / Backend / Database / Infra]
## Getting started
[Prerequisites + Installation + Dev server]
## Project structure
[Annotated tree]
## Conventions
[Naming, patterns, tests]
## Where to start?
[Key files to read first]
Constraints
- Adapt the level of detail to the target audience
- Include concrete examples and copy-paste commands
- Avoid unexplained jargon
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 · 54 lines · 34 tokens per session scan A 1e34430fec68
doc-onboard is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 322 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-31.
Other agents, from other repositories
reflector
Extracts structured lessons from successes and failures.
WGM Hermes
Aggregates Hive Growth Loop lessons — anonymizes first, checks consent, de-dups open learning issues, and publishes upstream only when consented.
docs-architect
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.
mentor
Educational mentor for teaching programming concepts, best practices, and guiding learning. Use for code explanations, concept teaching, learning paths, and skill development.
security-analyst
Security vulnerability analyst for authentication, authorization, secrets, input validation. Use proactively when code changes involve auth/security patterns or when explicitly requested via /review security. Activates for auth/, security/, middleware/ paths and keywords: auth, jwt, oauth, session, password, secret…
java-backend
Java Backend Execution Agent (Spring Boot / Quarkus).