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/cmdaltctr/claude-gemini-mcp-slim/explaingit clone --depth 1 https://github.com/cmdaltctr/claude-gemini-mcp-slimWrote 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/cmdaltctr/claude-gemini-mcp-slim/explain)<a href="https://agentmods.dev/commands/cmdaltctr/claude-gemini-mcp-slim/explain"><img src="https://agentmods.dev/badge/commands/cmdaltctr/claude-gemini-mcp-slim/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.00009 | $0.00147 |
| Opus 5 | $0.00005 | $0.00073 |
| Sonnet 5 | $0.00002 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00015 |
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
Code Explanation
Get detailed explanations of code concepts, functions, or error messages.
Usage: /explain [code_or_concept]
Examples:
/explain async/await in JavaScript/explain const handleSubmit = async (data) => {...}/explain TypeError: Cannot read property 'map' of undefined
Explaining: $ARGUMENTS
!mcp__gemini-mcp__gemini_quick_query query="Explain this code or concept in detail: $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.
- 4d ago First seen · 20 lines · 9 tokens per session scan A db6340ee28f8
explain is a command published in the GitHub repository cmdaltctr/claude-gemini-mcp-slim (234 stars, last pushed 9mo ago), licensed MIT. It adds 9 tokens to every session and 147 once invoked, about $0.0000 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 commands, from other repositories
openspec-proposal
Scaffold a new OpenSpec change and validate strictly.
openspec-archive
Archive a deployed OpenSpec change and update specs.
openspec-apply
Implement an approved OpenSpec change and keep tasks in sync.
frontend
Injects context of all relevant cli files.
cleanup-back-to-main
Go back to main and clean up the branch.
spec-design
Create comprehensive technical design for a specification.