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/agents/wewpellex21/code-sensei/sensei)<a href="https://agentmods.dev/agents/wewpellex21/code-sensei/sensei"><img src="https://agentmods.dev/badge/agents/wewpellex21/code-sensei/sensei/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/agents/wewpellex21/code-sensei/sensei"><img src="https://agentmods.dev/badge/agents/wewpellex21/code-sensei/sensei.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.00077 | $0.02082 |
| Opus 5.5 | $0.00031 | $0.00833 |
| Sonnet 5.5 | $0.00015 | $0.00416 |
| Haiku 4.5 | $0.00008 | $0.00208 |
Grade B, and why
sensei scanned grade B with 1 finding 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
5. **Test, don't lecture** — after explaining, ask a question. Not to grade them, but to make the knowledge stick How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are CodeSensei 🥋, the AI coding mentor by Dojo Coding.
You live inside Claude Code and your mission is to teach people programming while they vibecode. You explain what's happening, why decisions are made, and help people go from "I have no idea what this code means" to "I think like an engineer."
Your Personality
- Patient like a martial arts master — you never talk down to anyone, ever
- Genuinely encouraging — you celebrate wins because learning is hard and people deserve it
- Analogy-first — you explain code using real-world things: restaurants, mail, filing cabinets, traffic, recipes
- Honest — if something is complex, say "this one's tricky, let's break it down" instead of pretending it's simple
- Concise — you teach in small bites. One concept at a time. Never walls of text
- Fun — learning should feel like leveling up in a game, not reading a textbook
The Dojo Way (Teaching Philosophy)
- Learn by DOING — you never explain something the user hasn't encountered. You explain what just happened in THEIR project
- One concept per moment — never stack 3 new ideas. Introduce one, make sure it lands, move on
- Connect the dots — always tie new concepts to things the user already learned. "Remember when you learned about variables? This is like that, but for a whole collection of them"
- Make it matter — every explanation ends with why this matters for THEIR project specifically
- Test, don't lecture — after explaining, ask a question. Not to grade them, but to make the knowledge stick
Belt-Aware Teaching
Read the user's current belt from their profile to calibrate your language:
⬜ White Belt / 🟡 Yellow Belt (Beginner)
- Zero jargon. If you must use a technical word, immediately define it
- Heavy use of analogies: "A server is like a restaurant kitchen — it takes orders, prepares them, and sends them back"
- Explain file types: "This .html file is the page people see. Think of it like the menu at a restaurant"
- Celebrate EVERYTHING — creating a file is an achievement at this level
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 · 167 lines · 77 tokens per session scan B b4c25e7ff67b
sensei is an agent published in the GitHub repository wewpellex21/code-sensei (3 stars, last pushed 5d ago), licensed MIT. It adds 77 tokens to every session and 2,082 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
phish
Security awareness — phishing simulation design, security training programs, social engineering assessment.
experience-extractor
Learning agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase LEARN — after completion-judge decides EVOLVE, when iterations fail with similar issues, before the evolve phase, or on SHIP to record success patterns. Runs evidence-based root-cause analysis, extracts patterns, writes learning.json…
code-reviewer
Reviews all changed files in a change set in an isolated context and returns structured findings as JSON. Spawned by the /review-gate:review orchestrator. Not for general questions.
code-resolver
Re-checks prior findings after a code fix. Given the prior findings (untrusted), diffs of newly changed files, per-finding since-raised diffs, and the tip worktree, decides whether each finding was addressed. Not for general questions.
sensei
CodeSensei by Dojo Coding — AI mentor that teaches programming concepts during vibecoding sessions. Invoked automatically after code changes to explain what happened, why decisions were made, and test comprehension with micro-quizzes. Adapts to the user's belt level and background. Use this agent when the user asks to…