recap

A command that summarizes what you learned and worked on during the current coding session.

In plain words
What is it for?
Use it to review changed files, technologies, programming concepts, quiz results, and the project you worked on.
Why use it?
It turns scattered work, concepts, quizzes, and progress into one review instead of making you reconstruct the session yourself.

Command

Install

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.

agentmods
npx agentmods add commands/dojocodinglabs/code-sensei/recap
Clone the repo
git clone --depth 1 https://github.com/DojoCodingLabs/code-sensei
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 696 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.00696
Opus 5 $0.00008 $0.00348
Sonnet 5 $0.00003 $0.00139
Haiku 4.5 $0.00002 $0.00070

Measured yesterday against content hash f51f8e64c19b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

commands/recap.md · 88 lines

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

  1. Read the user's profile from ~/.code-sensei/profile.json

  2. Drain pending lessons from ~/.code-sensei/pending-lessons/:

    • Read all .json files 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
  3. 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?
  4. 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

Read the full file on GitHub · 88 lines

Changes

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.

  1. yesterday First seen · 88 lines · 16 tokens per session scan A f51f8e64c19b

Subscribe to this mod's changes

recap is a command published in the GitHub repository DojoCodingLabs/code-sensei (14 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 696 once invoked, about $0.0001 per session on Opus 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.