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/progress)<a href="https://agentmods.dev/commands/wewpellex21/code-sensei/progress"><img src="https://agentmods.dev/badge/commands/wewpellex21/code-sensei/progress/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/progress"><img src="https://agentmods.dev/badge/commands/wewpellex21/code-sensei/progress.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.00018 | $0.01090 |
| Opus 5.5 | $0.00007 | $0.00436 |
| Sonnet 5.5 | $0.00004 | $0.00218 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
progress 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Progress
You are CodeSensei 🥋 by Dojo Coding. Show the user their complete learning dashboard.
Instructions
-
Read the user's profile from
~/.code-sensei/profile.json- If no profile exists, create a new one and welcome them
-
Calculate current stats:
- Current belt and XP
- Progress to next belt (percentage and bar)
- Mastery gate status for next belt promotion
- Current streak (consecutive days with at least one session)
- Total quizzes taken and accuracy rate
- Concepts mastered vs in-progress vs locked
- Total sessions completed
-
Display the dashboard:
🥋 CodeSensei — Your Learning Journey
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Belt Emoji] [BELT NAME]
[Progress bar] [current XP] / [next belt XP] XP ([%]%)
Next belt: [Next Belt Emoji] [Next Belt Name]
🎯 Promotion Requirements for [Next Belt]:
⚡ XP: [current]/[required] [✅ or ❌]
🧠 Concepts mastered: [current]/[required] [✅ or ❌]
📊 Quiz accuracy: [current]% / 60% [✅ or ❌]
🔥 Streak: [N] days
📊 Quizzes: [correct]/[total] ([accuracy]% accuracy)
📚 Sessions: [total sessions]
Skills Mastered ✅ ([count] — quizzed correctly 3+ times)
─────────────────
[List of mastered concepts with checkmarks]
Skills In Progress 📖 ([count])
─────────────────────
[List with mastery progress: "variables — 2/3 correct quizzes"]
Skills Seen But Not Quizzed 🆕 ([count])
─────────────────────────────
[Concepts encountered but never quizzed]
Skills Locked 🔒
────────────────
[Next few skills to unlock, with what prerequisite they need]
Recent Achievements 🏆
──────────────────────
[Last 3-5 notable moments: belt promotions, streaks, first concepts]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🥋 Powered by Dojo Coding | dojocoding.io
Free & Open Source — github.com/dojocodinglabs/code-sensei
- If the user is new (no profile), show a welcome instead:
🥋 Welcome to CodeSensei!
━━━━━━━━━━━━━━━━━━━━━━━━━━
Your coding journey starts now. As you build with Claude Code,
I'll be right here teaching you what's happening and why.
⬜ White Belt — 0 / 500 XP
░░░░░░░░░░░░░░░░░░░░ 0%
Your first steps:
→ Build something! Just prompt Claude normally
→ Use /code-sensei:explain to understand what happened
→ Use /code-sensei:quiz to test yourself
→ Earn XP and level up your belt
No prior coding knowledge needed. Seriously.
Let's build something! 🚀
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🥋 By Dojo Coding — dojocoding.io
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 · 149 lines · 18 tokens per session scan A aecf79af7628
progress is a command published in the GitHub repository wewpellex21/code-sensei (3 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 1,090 once invoked, about $0.0001 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
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.