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/NikiforovAll/claude-code-rulesWrote 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/nikiforovall/claude-code-rules/explain)<a href="https://agentmods.dev/commands/nikiforovall/claude-code-rules/explain"><img src="https://agentmods.dev/badge/commands/nikiforovall/claude-code-rules/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/nikiforovall/claude-code-rules/explain"><img src="https://agentmods.dev/badge/commands/nikiforovall/claude-code-rules/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.00000 | $0.00528 |
| Opus 5.5 | $0.00000 | $0.00211 |
| Sonnet 5.5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Target: $1, Level : $2, Format : $3, Context : $4
Behavioral Flow
- Analyze: Examine target code, concept, or system for comprehensive understanding
- Assess: Determine audience level and appropriate explanation depth and format
- Structure: Plan explanation sequence with progressive complexity and logical flow
- Generate: Create clear explanations with examples, diagrams, and interactive elements
- Validate: Verify explanation accuracy and educational effectiveness
Key behaviors:
- Framework-specific explanations via Context7 integration via MCP
- Adaptive explanation depth based on audience and complexity
Tool Coordination
- Read/Grep/Glob: Code analysis and pattern identification for explanation content
- TodoWrite: Progress tracking for complex multi-part explanations
- Task: Delegation for comprehensive explanation workflows requiring systematic breakdown
Key Patterns
- Progressive Learning: Basic concepts → intermediate details → advanced implementation
- Framework Integration: Context7 documentation → accurate official patterns and practices
- Multi-Domain Analysis: Technical accuracy + educational clarity + security awareness
- Interactive Explanation: Static content → examples → interactive exploration
Examples
Basic Code Explanation
/explain authentication.js --level basic
# Clear explanation with practical examples for beginners
# Educator persona provides learning-optimized structure
Framework Concept Explanation
/explain react-hooks --level intermediate --context react
# Structured explanation with progressive complexity
System Architecture Explanation
/explain microservices-system --level advanced --format interactive
# Architect persona explains system design and patterns
# Interactive exploration with Sequential analysis breakdown
Security Concept Explanation
/explain jwt-authentication --context security --level basic
# Security persona explains authentication concepts and best practices
# Framework-agnostic security principles with practical examples
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 · 69 lines · 0 tokens per session scan A 0dfb78b7f18d
explain is a command published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 15d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 528 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
code-review-teach
Educational code review that teaches while reviewing. Provides constructive feedback, explains best practices, discusses trade-offs, and helps developers improve their coding skills.
concept-deep-dive
Deep dive into programming concepts with layered explanations, real-world examples from your codebase, practical applications, and interactive learning.
practice-exercise
Generate personalized coding exercises based on your codebase patterns and skill level. Includes progressive hints, solution review, and hands-on learning challenges.
workflow-tracer
Trace complete workflows and user journeys through the codebase.
business-logic-map
Extract and map all business logic, rules, and workflows from the codebase.
progress
View your CodeSensei learning dashboard — belt rank, XP, streaks, and skills.