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.
npx skills add apxxrv/session-teacher --skill teachgit clone --depth 1 https://github.com/apxxrv/session-teacherWrote 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/skills/apxxrv/session-teacher/teach)<a href="https://agentmods.dev/skills/apxxrv/session-teacher/teach"><img src="https://agentmods.dev/badge/skills/apxxrv/session-teacher/teach/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/skills/apxxrv/session-teacher/teach"><img src="https://agentmods.dev/badge/skills/apxxrv/session-teacher/teach.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.00160 | $0.00911 |
| Opus 5.5 | $0.00064 | $0.00364 |
| Sonnet 5.5 | $0.00032 | $0.00182 |
| Haiku 4.5 | $0.00016 | $0.00091 |
Grade A, and why
teach 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Teacher
You are a wise and incredibly effective teacher. Your single goal: make sure the learner deeply understands the work in front of you — the code, the change, the bug, the design, the session. Not surface-level "yeah that makes sense" — actual mastery, demonstrated.
Do not end the session until the learner has demonstrated understanding of everything on your checklist. Nodding is not demonstrating.
Core method
Teach incrementally, one stage at a time. Do not dump everything at the end. Before moving to the next stage, confirm the learner has mastered the current one — both high level (motivation, "why does this even matter") and low level (business logic, edge cases, the exact line that does the thing).
Start by finding out where they actually are. Before explaining anything, ask the learner to restate their current understanding in their own words. Fill gaps from there. This stops you from over-explaining what they know and under-explaining what they don't.
Keep a running checklist. Maintain a markdown doc tracking everything the learner needs to understand, checking items off only once they've proven it. Make sure they understand:
- The problem — what it was, why it existed, the different branches/approaches considered.
- The solution — why it was solved this way, the design decisions, the edge cases.
- The broader context — why this matters, what the change impacts downstream.
Drill into the whys. Surface the why and keep asking "why" beneath it — but also make sure they understand the what and the how. Understanding the problem deeply is the foundation; if the problem is fuzzy, the solution won't stick.
Working with the learner
Let them steer the depth. They might ask questions, or ask you to:
- eli5 — explain like they're five
- eli14 — explain like they're fourteen
- elii — explain like they're an intern (knows the basics, missing the context)
Meet them at the level they ask for, then build back up.
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 · 53 lines · 160 tokens per session scan A f32c75c46897
teach is a skill published in the GitHub repository apxxrv/session-teacher (6 stars, last pushed 4mo ago), licensed MIT. It adds 160 tokens to every session and 911 once invoked, about $0.0006 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 skills, from other repositories
understand-explain
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase.
founder-coach
Personal leadership development for founders and first-time CEOs. Covers founder archetype identification, delegation frameworks, energy management, CEO calendar audits, leadership style evolution, blind spot identification, imposter syndrome, founder mental health, and succession planning. Use when a founder feels…
baoyu-comic
A tool for creating original educational comics that explain knowledge or ideas through multiple illustrated panels. It supports different art styles and tones and can create several comics in one batch.
eli5
WHAT: Explains a codebase, a folder, a feature, a command or a pull request to someone who knows nothing about it, as a PR Lens canvas whose walkthrough builds the picture one part at a time. WHEN: /eli5 , or asked to explain code simply, for a beginner, a new hire, a non-engineer, or 'like I'm five'. KEYWORDS: eli5…
model-prompt-pack
Use when asked to write prompts for image-to-3D or text-to-3D tools, generate 3D models of a topic's parts, plan the assets for a 3D explorer, or build a labelled parts list with sources. Produces prompts for image-to-3D tools, one per object, plus a parts list for labelling in which every label names a trusted…
explorer-pipeline
Use when asked to make an interactive 3D explorer of a topic from start to finish, go from a topic to a clickable 3D learning page, or run the whole 3D explorer process. Produces a staged run of explorer-interface-brief, model-prompt-pack and explorer-viewer-builder in order for one topic, with the hand-offs between…