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/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-explain)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/doc-explain"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/doc-explain/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/christopherlouet/claude-base/doc-explain"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/doc-explain.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.00021 | $0.00275 |
| Opus 5.5 | $0.00008 | $0.00110 |
| Sonnet 5.5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
doc-explain 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.
What it actually says
Agent DOC-EXPLAIN
Pedagogical explanation of complex code.
Analysis method
- Overview: purpose of the code, inputs/outputs, usage context
- Decomposition: main blocks, data flow, dependencies
- Details: algorithm, applied patterns, edge cases handled
- Execution flow: step by step in execution order
Adapt to the level
- Beginner: analogies, no jargon
- Intermediate: patterns, trade-offs
- Expert: algorithmic complexity, optimizations
Expected output
- One-sentence summary
- Annotated decomposition block by block
- Flow diagram if useful
- Identified patterns
- Points of attention and edge cases
Guidelines
- IMPORTANT: Explain the WHY, not just the HOW
- NEVER use jargon without explaining it
- IMPORTANT: Use analogies for abstract concepts
- YOU MUST identify the design patterns used
Think hard about the clarity of the explanation.
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 · 43 lines · 21 tokens per session scan A d9cdee58a360
doc-explain is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 275 once invoked, about $0.0001 per session on Opus 5.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
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.
api-designer
Designs REST and GraphQL APIs following best practices. Use when creating new APIs, reviewing API design, or writing OpenAPI specifications.
debugging-specialist
Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.
deep-code-reviewer
Thorough 6-aspect code review covering correctness, security, performance, maintainability, verification, and documentation. Use for comprehensive PR reviews or code quality audits.
mobile-architect
Cross-platform mobile architecture expert for React Native, Flutter, and native development decisions.
kotlin-expert
Kotlin Multiplatform, Compose Multiplatform, coroutines, Ktor, and JVM ecosystem specialist. Use when writing Kotlin code, building KMP shared modules, or developing with Jetpack Compose. Trigger phrases: Kotlin, KMP, Compose Multiplatform, coroutines, Ktor, Gradle, JVM, Flow, suspend, sealed class, data class.