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 skills add travisjneuman/.claude --skill agent-code-explainergit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/skills/travisjneuman/.claude/agent-code-explainer)<a href="https://agentmods.dev/skills/travisjneuman/.claude/agent-code-explainer"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-code-explainer/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/skills/travisjneuman/.claude/agent-code-explainer"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-code-explainer.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.00038 | $0.00449 |
| Opus 5.5 | $0.00015 | $0.00180 |
| Sonnet 5.5 | $0.00008 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
agent-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 16d 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
Your task
$ARGUMENTS
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.
- 16d ago First seen · 114 lines · 38 tokens per session scan A 17e8e40fe2c1
agent-code-explainer is a skill published in the GitHub repository travisjneuman/.claude (101 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 449 once invoked, about $0.0002 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-09-30.
Other skills, from other repositories
explain
Explain something in depth on request. Use when the user writes "???" - alone, or placed directly after a reference, statement, or term - which means "explain that in more detail, with a concrete example AND consequences". Also invoked by the /credo:explain command. Treat the pointed-at subject as the thing to…
skill-discovery
Find related skills via dependency graph analysis, discover learning paths, and identify skill clusters.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.