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/spideynolove/claude-dotfilesWrote 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/spideynolove/claude-dotfiles/explain-code)<a href="https://agentmods.dev/commands/spideynolove/claude-dotfiles/explain-code"><img src="https://agentmods.dev/badge/commands/spideynolove/claude-dotfiles/explain-code/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/spideynolove/claude-dotfiles/explain-code"><img src="https://agentmods.dev/badge/commands/spideynolove/claude-dotfiles/explain-code.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.00012 | $0.00399 |
| Opus 5.5 | $0.00005 | $0.00160 |
| Sonnet 5.5 | $0.00002 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
explain-code 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
Code Explain
Explains how code works in detail.
Usage
# Show a file and ask for explanation
cat <file>
"Explain how this code works"
Basic Examples
# Understand Rust ownership
cat main.rs
"Explain the ownership and lifetimes in this Rust code"
# Explain an algorithm
grep -A 50 "quicksort" sort.rs
"How does this sorting work? What's its time complexity?"
# Explain design patterns
cat factory.rs
"What design pattern is this? What are the benefits?"
Collaboration with Claude
# Beginner-friendly explanation
cat complex_function.py
"Explain this code line by line for someone new to programming"
# Performance check
cat algorithm.rs
"Find performance problems and how to fix them"
# Visual explanation
cat state_machine.js
"Show me the flow with ASCII diagrams"
# Security check
cat auth_handler.go
"What security issues do you see?"
Detailed Examples
# Complex logic breakdown
cat recursive_parser.rs
"Break down this recursive parser:
1. How does it flow?
2. What does each function do?
3. How are edge cases handled?
4. What could be better?"
# Async code explanation
cat async_handler.ts
"Explain this async code:
1. How do the Promises flow?
2. How are errors handled?
3. What runs in parallel?
4. Could this deadlock?"
# Architecture overview
ls -la src/ && cat src/main.rs src/lib.rs
"Explain how this project is structured"
What You'll Get
Not just what the code does, but also:
- Why it's written that way
- What benefits it provides
- What problems might come up
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 · 85 lines · 12 tokens per session scan A 35e342832eb4
explain-code is a command published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 399 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-31.
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.
start-1
A guided beginner course for product managers learning Claude Code, a coding assistant that works from the command line.