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 smileynet/teach-me --skill teachgit clone --depth 1 https://github.com/smileynet/teach-meWrote 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/smileynet/teach-me/teach)<a href="https://agentmods.dev/skills/smileynet/teach-me/teach"><img src="https://agentmods.dev/badge/skills/smileynet/teach-me/teach.svg" alt="Measured on agentmods" 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.00046 | $0.02823 |
| Opus 5 | $0.00023 | $0.01411 |
| Sonnet 5 | $0.00009 | $0.00565 |
| Haiku 4.5 | $0.00005 | $0.00282 |
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 today.
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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The user wants to learn something. This is stateful — they intend multiple sessions.
Teaching Workspace
The current directory is the workspace. State lives in:
MISSION.md— why the learner wants this (grounds everything)RESOURCES.md— verified sources with trust ratings (populated BEFORE lessons)lessons/*.html— self-contained HTML lessons (one concept each)reference/*.html— scannable lookup companions to lessonslearning-records/*.md— demonstrated understanding (drives ZPD)assets/— shared components (CSS, JS, diagrams)NOTES.md— learner preferences, working notes
Workflow
- Mission first. If
MISSION.mdis empty, ask why they're learning this. Don't produce a lesson without a mission. - Research the domain. Identify 3-6 subtopics, dispatch research, populate RESOURCES.md. See references/research-methodology.md. This is a hard gate — no lesson from parametric memory.
- Find the ZPD. Read learning records, determine what to teach next.
- Write the lesson. One concept, one win. Read the scaffold from
assets/scaffolds/lesson.htmlfirst. Follow references/lesson-components.md for theming, diagrams, glossary, exercises. - Write the reference doc. Simultaneously — same authoring pass. Scannable, lookup-oriented.
- Generate SR questions. 3-5 conceptual questions with criteria-based answers. See references/sr-question-design.md.
- Run quality gates.
mise run sr:check+ the publish checklist below.
Lesson Shape
- Opening: end-state preview → context (why this matters) → teach
- Tone: knowledgeable colleague at a whiteboard. Direct, assumes intelligence.
- Style: Grade 8-10 reading level. Short paragraphs. Plain words. One clause per sentence max.
- Claims: Cited or framed as general. Never invent specific numbers.
- Visuals: Every conceptual section has a diagram. Labels ON the diagram.
- Limitations: Frame as "What to pursue alongside this" — actionable recommendations, not defensive disclaimers.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed cbcd34b09147
- 7d ago First seen · 215 lines · 46 tokens per session scan A e85e6bd7cb65
teach is a skill published in the GitHub repository smileynet/teach-me (3 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 2,823 once invoked, about $0.0002 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-31.
Other skills, from other repositories
anki
Anki spaced repetition learning system reference. Covers the science of SRS and SM-2 algorithm, card design principles, optimal deck settings, FSRS scheduler, study workflow, essential add-ons, custom templates, filtered decks, and AnkiConnect API.
reading-metaskill
A reading and learning guide based on building a regular reading habit, choosing books, and understanding difficult subjects through original works and explanation.
textbook-distillation
Turn a textbook or long-form source into a self-paced learning track: chapter map, lesson plan, then self-contained HTML lecture notes (styled as the human specifies) with worked examples, exercises, and checkpoint questions. Read this for "lecture notes" / "study notes" / "course" / "syllabus" requests from a…
learning-notes-automation
A workflow for turning videos, podcasts, and articles into structured learning notes. It extracts key ideas and creates flashcards that can be imported into Anki, a spaced-repetition study app.
antivibe
Code learning and audit framework. Analyze any codebase — new, legacy, or AI-generated — and produce educational explanations or architectural audits. Use when the user wants to understand WHAT and WHY behind any code, not just accept it.
growth-mindset
Applies Carol Dweck's growth mindset framework to individual resilience and organizational culture, distinguishing between fixed mindset (ability is innate) and growth mindset (ability develops through effort and strategy). Use when processing failure and setbacks, reframing team responses to challenges, designing…