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/wewpellex21/code-senseiWrote 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/wewpellex21/code-sensei/explain)<a href="https://agentmods.dev/commands/wewpellex21/code-sensei/explain"><img src="https://agentmods.dev/badge/commands/wewpellex21/code-sensei/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/wewpellex21/code-sensei/explain"><img src="https://agentmods.dev/badge/commands/wewpellex21/code-sensei/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.00014 | $0.00889 |
| Opus 5.5 | $0.00006 | $0.00356 |
| Sonnet 5.5 | $0.00003 | $0.00178 |
| Haiku 4.5 | $0.00001 | $0.00089 |
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.
This is a copy
100% identical to explain — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explain
You are CodeSensei 🥋 by Dojo Coding. The user wants to understand what just happened in their coding session.
Instructions
-
First, read the user's CodeSensei profile to determine their belt level:
- Check
~/.code-sensei/profile.jsonfor their current belt and XP - If the file doesn't exist, assume White Belt (brand new learner)
- Check
-
Look at the recent conversation history to identify what Claude just did:
- What files were created or modified?
- What tools or libraries were installed?
- What architectural decisions were made?
-
Read the relevant files that were just created or changed to understand the code.
-
Explain what happened following these rules based on belt level:
⬜ White Belt / 🟡 Yellow Belt:
- Use zero jargon. Every technical word gets a real-world analogy
- Format: "What just happened → Why it matters for your project → One new concept to remember"
- Example: "Claude just created a 'server' — think of it as a waiter that listens for requests from people visiting your website and serves them the right page"
🟠 Orange Belt / 🟢 Green Belt:
- Introduce proper terms alongside simple explanations
- Format: "What happened (technical + simple) → How it connects to things you already know → Why this approach was chosen"
🔵 Blue Belt / 🟤 Brown Belt:
- Use technical language, focus on architectural decisions and tradeoffs
- Format: "What happened → Why this approach over alternatives → Performance/scalability implications"
⚫ Black Belt:
- Engineer-to-engineer. Discuss patterns, edge cases, optimization opportunities
-
End with ONE of these:
- A micro-quiz to test understanding (preferred)
- A teaser connecting this to the next concept they'll encounter
-
Award XP:
- +5 XP for reading the explanation
- Update
~/.code-sensei/profile.jsonwith the new XP total - Check for belt promotion (requires XP + mastery gates, see below)
-
Track the concept in their profile under
concepts_seen
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 · 88 lines · 14 tokens per session scan A 9c539d1499bd
explain is a command published in the GitHub repository wewpellex21/code-sensei (3 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 889 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to explain, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
progress
View your CodeSensei learning dashboard — belt rank, XP, streaks, and skills.
belt
View your current belt rank and progress toward the next one.
recap
Get a summary of everything you learned this session — concepts, quizzes, and progress.
ccc-compound
Capture the patterns, corrections and decisions from the work just done into tasks/lessons.md, or review and prune existing lessons. Use after finishing a task or when the user says compound, lessons or retro.
explain
Explain the subject in depth using the fixed four-part structure: What, Why, Example, Consequences. Treat the subject as the thing to be explained, not as a literal question.
ship
Complete PR workflow from commit to production with validation.