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 commands/rohitg00/awesome-claude-code-toolkit/explaingit clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkitWhat 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.00000 | $0.00362 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
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 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
Explain a code file, function, or concept in clear, structured language.
Steps
- Read the target code (file path, function name, or code block).
- Determine the audience level from context (junior, mid, senior, non-technical).
- Analyze the code structure:
- Purpose: What problem does this code solve?
- Inputs: What data does it receive and from where?
- Processing: What transformations or logic does it apply?
- Outputs: What does it produce or modify?
- Side effects: What external state does it change?
- Break down complex sections:
- Explain algorithms step by step.
- Clarify language-specific idioms or patterns.
- Describe the data flow through the code.
- Identify design patterns in use (Observer, Strategy, Factory, etc.).
- Note any non-obvious behavior, gotchas, or edge cases.
- Provide analogies for complex concepts when appropriate.
Format
## <File/Function Name>
### Purpose
<one-sentence summary>
### How It Works
1. <step-by-step explanation>
### Key Concepts
- <pattern/concept>: <explanation>
### Gotchas
- <non-obvious behavior to be aware of>
### Dependencies
- <what this code depends on>
- <what depends on this code>
Rules
- Explain the "why" not just the "what"; anyone can read the code.
- Use concrete examples with real values from the codebase.
- Avoid jargon unless explaining it; match the audience level.
- Keep explanations under 100 lines; link to deeper resources for complex topics.
- Do not restate code as prose; explain the intent and reasoning behind it.
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 · 50 lines · 0 tokens per session scan A cdea455a5552
explain is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,578 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 362 tokens. 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 commands, from other repositories
create-prompt
Create a new prompt that another Claude can execute.
create-slash-command
Create a new slash command following best practices and patterns.
remember
Save something to agent memory - picks project or user scope automatically from context.
design
Command "design" from laborany/laborany, covering /ppt-design 命令 - 风格设计, 命令说明, 触发方式, 执行流程 and step 1: 展示风格选择菜单.
brainstorm
You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
update
Analyze the codebase and update documentation.