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/Dev-GOM/claude-code-marketplaceWrote 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/commands/dev-gom/claude-code-marketplace/explain)<a href="https://agentmods.dev/commands/dev-gom/claude-code-marketplace/explain"><img src="https://agentmods.dev/badge/commands/dev-gom/claude-code-marketplace/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/commands/dev-gom/claude-code-marketplace/explain"><img src="https://agentmods.dev/badge/commands/dev-gom/claude-code-marketplace/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.00010 | $0.00274 |
| Opus 5.5 | $0.00004 | $0.00110 |
| Sonnet 5.5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00027 |
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 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
Provide a clear, comprehensive explanation of the code, concept, or system architecture.
Explanation Style:
-
Start with the Big Picture
- What is this code/system for?
- What problem does it solve?
- How does it fit into the larger project?
-
Break Down the Details
- Explain each major component
- Describe how components interact
- Highlight key algorithms or patterns
-
Walk Through the Flow
- Trace execution paths
- Show data transformations
- Explain control flow
-
Highlight Important Concepts
- Design patterns used
- Best practices applied
- Trade-offs and decisions made
-
Provide Examples
- Show usage scenarios
- Give concrete examples
- Demonstrate edge cases
-
Connect to Fundamentals
- Link to underlying principles
- Reference related concepts
- Suggest further learning resources
Explanation Levels:
- Beginner: Simple terms, lots of context
- Intermediate: Technical details, common patterns
- Expert: Advanced concepts, trade-offs, alternatives
Adjust explanation depth based on your needs. What would you like me to explain?
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 · 47 lines · 10 tokens per session scan A 9681b4944d81
explain is a command published in the GitHub repository Dev-GOM/claude-code-marketplace (97 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 274 once invoked, about $0.0000 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-30.
Other commands, from other repositories
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-0-8
A Japanese-language command that displays the current project setup progress.
setup-m365cli.es
Lesson command — Setup de M365 CLI.
prep-role
Deep prep for a specific role's interview process. The user wants to know what to expect, how to win, and what kills candidates at their level.
setup-vercel.es
Command "setup-vercel.es" from minicoohei/ai-agent-camp, covering configuración de vercel cli, step 0: verificar progreso de configuración, lo que hará en esta sesión, verificación de preparación and step 1: crear cuenta de vercel.