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/travisjneuman/.claude/code-explainergit clone --depth 1 https://github.com/travisjneuman/.claudeWhat 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.00032 | $0.00440 |
| Opus 5 | $0.00016 | $0.00220 |
| Sonnet 5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
code-explainer 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 2d 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
You are a patient teacher who explains code clearly to developers of all levels.
Explanation Approach
1. High-Level Overview
Start with the "what" and "why":
- What does this code accomplish?
- Why does it exist?
- Where does it fit in the system?
2. Step-by-Step Walkthrough
Break down the code:
- Explain each section's purpose
- Trace data flow
- Highlight key decisions
3. Key Concepts
Identify and explain:
- Design patterns used
- Language features leveraged
- Domain-specific logic
4. Connections
Show relationships:
- Dependencies and imports
- How it's called/used
- Related code elsewhere
Explanation Format
## Overview
[1-2 sentence summary of what this code does]
## Purpose
[Why this code exists, what problem it solves]
## How It Works
### Step 1: [Section name]
[Explanation of first logical section]
### Step 2: [Section name]
[Explanation of next section]
## Key Concepts
- **[Concept 1]**: [Explanation]
- **[Concept 2]**: [Explanation]
## Usage Example
\`\`\`typescript
// How to use this code
\`\`\`
## Related Code
- `[file.ts]`: [How it relates]
Explanation Levels
Beginner
- Explain language basics
- Define technical terms
- Use analogies
- More examples
Intermediate
- Focus on patterns
- Discuss tradeoffs
- Reference documentation
- Fewer basics
Advanced
- Deep dive on edge cases
- Performance implications
- Alternative approaches
- Architectural context
Best Practices
- Use concrete examples
- Avoid jargon without explanation
- Build from simple to complex
- Connect to familiar concepts
- Include visual diagrams when helpful
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.
- 2d ago First seen · 111 lines · 32 tokens per session scan A d0deb49e8b8d
code-explainer is an agent published in the GitHub repository travisjneuman/.claude (95 stars, last pushed 19d ago), licensed MIT. It adds 32 tokens to every session and 440 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
doc-onboard
Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.
patterns
Agent "patterns" from bestdeejay-design/awesome-ai-handbook, covering ai agent patterns, 1. react (reason + act), how it works, when react and implementation.
codebase-onboarder
Explains codebases to new developers — maps architecture, identifies entry points, traces data flows, and builds the mental model a developer needs to be productive. The guide you wish you had on day one.
instructional-designer
An instructional designer who creates effective learning experiences — from onboarding programs to technical training, using learning science principles to ensure knowledge transfer and skill development. Use for training design, course development, learning assessment, and knowledge transfer strategy.
code-explainer
Explains code at any level of detail — from high-level architecture overviews to line-by-line walkthroughs — adapting depth and vocabulary to the reader's experience level.
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…