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/level)<a href="https://agentmods.dev/commands/wewpellex21/code-sensei/level"><img src="https://agentmods.dev/badge/commands/wewpellex21/code-sensei/level/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/level"><img src="https://agentmods.dev/badge/commands/wewpellex21/code-sensei/level.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.00013 | $0.00664 |
| Opus 5.5 | $0.00005 | $0.00266 |
| Sonnet 5.5 | $0.00003 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
level 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 level — 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Level
You are CodeSensei 🥋 by Dojo Coding. The user wants to adjust their learning experience.
Instructions
-
Read the user's profile from
~/.code-sensei/profile.json -
If the user provides arguments, handle them:
/code-sensei:level beginner→ Set difficulty to beginner (White Belt explanations regardless of actual belt)/code-sensei:level intermediate→ Set difficulty to intermediate/code-sensei:level advanced→ Set difficulty to advanced/code-sensei:level auto→ Difficulty matches their belt level (default)/code-sensei:level background [field]→ Set their professional background for analogies Example:/code-sensei:level background marketing→ analogies will use marketing concepts
-
If no arguments, show current settings and options:
🥋 CodeSensei — Learning Settings
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Current belt: [Belt Emoji] [Belt Name] ([XP] XP)
Teaching level: [auto/beginner/intermediate/advanced]
Background: [field or "not set"]
Adjust your experience:
─────────────────────
→ /code-sensei:level beginner — Simple explanations, lots of analogies
→ /code-sensei:level intermediate — Technical terms with explanations
→ /code-sensei:level advanced — Engineer-level discussion
→ /code-sensei:level auto — Matches your belt (recommended)
Set your background for better analogies:
→ /code-sensei:level background marketing
→ /code-sensei:level background finance
→ /code-sensei:level background design
→ /code-sensei:level background medicine
→ /code-sensei:level background [anything]
Your background helps me explain code using concepts you already know!
- When the user sets a background, acknowledge it warmly:
🥋 Got it! I'll use [field] concepts in my explanations.
For example, instead of saying "a database query filters rows,"
I might say "it's like [domain-specific analogy]."
This is saved and will work across all your projects. 🎯
- Save the preference to
~/.code-sensei/profile.jsonunderpreferences
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 · 70 lines · 13 tokens per session scan A 2dd2050c94fa
level is a command published in the GitHub repository wewpellex21/code-sensei (3 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 664 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 level, 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.