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 skills/poshan0126/dotclaude/explainnpx skills add poshan0126/dotclaude --skill explaingit clone --depth 1 https://github.com/poshan0126/dotclaudeWrote 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/poshan0126/dotclaude/explain)<a href="https://agentmods.dev/skills/poshan0126/dotclaude/explain"><img src="https://agentmods.dev/badge/skills/poshan0126/dotclaude/explain.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.00037 | $0.00330 |
| Opus 5 | $0.00018 | $0.00165 |
| Sonnet 5 | $0.00007 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
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 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
Explain $ARGUMENTS clearly.
Mode
If $ARGUMENTS includes the word verbose (for example, /explain my-function verbose), produce all five sections below. Strip the word verbose from the target name when interpreting what to explain.
Otherwise (the default), produce only sections 1 and 2 and stop. Day-to-day that's usually all you need.
Sections
1. One-sentence summary
What does it do, and why does it exist? One sentence.
2. Mental model
An analogy or metaphor that captures the core idea. Relate it to something the developer already knows. One short paragraph.
3. Visual diagram (verbose only)
Draw an ASCII diagram showing the data and control flow. Keep it readable:
Input -> [Step A] -> [Step B] -> Output
|
v
[Side Effect]
4. Key details (verbose only)
Walk through the important parts. Skip the obvious. Focus on:
- Non-obvious decisions (why this approach?)
- Edge cases and gotchas
- Dependencies and side effects
5. How to modify it (verbose only)
What would someone need to know to safely change this code? Where are the landmines?
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 · 46 lines · 37 tokens per session scan A 335ce34d8f54
explain is a skill published in the GitHub repository poshan0126/dotclaude (860 stars, last pushed 7d ago), licensed MIT. It adds 37 tokens to every session and 330 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…