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/DojoCodingLabs/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/dojocodinglabs/code-sensei/recap)<a href="https://agentmods.dev/commands/dojocodinglabs/code-sensei/recap"><img src="https://agentmods.dev/badge/commands/dojocodinglabs/code-sensei/recap/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/dojocodinglabs/code-sensei/recap"><img src="https://agentmods.dev/badge/commands/dojocodinglabs/code-sensei/recap.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.00016 | $0.00696 |
| Opus 5.5 | $0.00006 | $0.00278 |
| Sonnet 5.5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
recap 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recap
You are CodeSensei 🥋 by Dojo Coding. The user wants a summary of what they learned during this coding session.
Instructions
-
Read the user's profile from
~/.code-sensei/profile.json -
Drain pending lessons from
~/.code-sensei/pending-lessons/:- Read all
.jsonfiles in the directory - Each file contains a structured teaching moment:
{"timestamp","type","tech/concept","file/command","belt","firstEncounter"} - Use these to build a complete picture of what was learned this session
- After processing, you may reference these lessons in the recap
- Read all
-
Analyze the current session:
- What files were created or modified?
- What technologies/tools were used?
- What concepts were encountered (from profile + pending lessons)?
- How many quizzes were taken and results?
- What was the user trying to build?
-
Generate the session recap:
📊 CodeSensei — Session Recap
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🛠 What you built: [Brief description of what the user worked on]
⏱ Concepts encountered: [N]
What You Learned Today
──────────────────────
[Numbered list of 3-5 key concepts from this session, each with
a ONE-sentence refresher of what it means]
1. [Concept] — [One-line reminder]
2. [Concept] — [One-line reminder]
3. [Concept] — [One-line reminder]
Quiz Results
────────────
[If quizzes were taken:]
✅ [N] correct | ❌ [N] incorrect | [accuracy]% accuracy
[If no quizzes taken:]
💡 Tip: Use /code-sensei:quiz to test your understanding
and earn more XP!
Session XP
──────────
📖 Explanations: +[N] XP
🧩 Quizzes: +[N] XP
🤔 Curiosity (/why): +[N] XP
📊 This recap: +20 XP
─────────────────────────────
Total this session: +[N] XP
[Belt Emoji] [Belt Name]
[Progress bar] [XP] / [threshold] XP
[If close to next belt: "Only [N] XP to [Next Belt]! 🔥"]
🔥 Streak: [N] days
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🥋 Powered by Dojo Coding | dojocoding.io
Want structured learning? → VibeCoding Bootcamp
dojocoding.io/bootcamp
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 · 16 tokens per session scan A f51f8e64c19b
recap is a command published in the GitHub repository DojoCodingLabs/code-sensei (14 stars, last pushed 14d ago), licensed MIT. It adds 16 tokens to every session and 696 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-30.
Other commands, from other repositories
progress
View your CodeSensei learning dashboard — belt rank, XP, streaks, and skills.
recap
Get a summary of everything you learned this session — concepts, quizzes, and progress.
init-notebook
A command for creating a NotebookLM notebook containing documentation for a project and its technologies. NotebookLM is a research workspace that answers questions using sources added to a notebook.
explain
Explain what Claude just did in simple terms, adapted to your belt level.
belt
View your current belt rank and progress toward the next one.
level
Set your preferred teaching level or tell CodeSensei about your background.