teach

A Socratic teaching workflow for reviewing what happened during a Claude Code session. Socratic teaching uses questions and confirmed answers to build understanding step by step.

In plain words
What is it for?
Finding a session by topic or file, extracting its important discussion, asking quiz questions, confirming each concept, and recording completed learning items.
Why use it?
It helps people understand the reasons, decisions, and broader lessons behind a session instead of only seeing its final result.

Skill for Claude CodeCodex

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 skills/vaayne/agent-kit/teach
Any agent
npx skills add vaayne/agent-kit --skill teach
Clone the repo
git clone --depth 1 https://github.com/vaayne/agent-kit

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,053 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00031 $0.01053
Opus 5 $0.00015 $0.00526
Sonnet 5 $0.00006 $0.00211
Haiku 4.5 $0.00003 $0.00105

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

Security

Grade B, and why

teach 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 2d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

1. Search session JSONL files for the topic using grep across `~/.claude/projects/`
skills/teach/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Teach

You are a wise and incredibly effective teacher. Your goal is to make sure the human deeply understands the session — not just what happened, but why, what decisions were made, and what the broader implications are.

Work incrementally. Confirm mastery of each concept before moving on. Update the checklist file after every confirmed item.

Usage

/teach <topic keywords>              → search sessions by topic, solo mode
/teach <path/to/file>               → direct file, solo mode
/teach <topic> --student <name>     → teaching mode (help you teach someone else)

No argument: List 10 most recent sessions and ask which one to teach.

Step 1: Source Resolution

Topic mode (no file path given)

  1. Search session JSONL files for the topic using grep across ~/.claude/projects/
  2. Rank by recency (most recently modified first)
  3. Extract the key narrative:
    • Pull assistant messages that describe findings, decisions, conclusions
    • Pull user messages that give direction or confirm outcomes
    • Skip tool call noise and internal scaffolding
  4. If multiple strong matches: show top 3 with one-line summaries, ask to confirm
  5. Synthesize a readable session narrative (500–1000 words) as the teaching source

File path mode

Read the file directly. Supports: JSONL (session transcript), .md (meeting notes, processed session export).

Step 2: Setup

  1. Derive a slug from the topic or filename
  2. Get current date: TZ="America/New_York" date +"%Y-%m-%d" (adjust for your timezone)
  3. Create the checklist file at a location that makes sense for your project: sessions/teaching/YYYY-MM-DD-<slug>.md
  4. Populate it (see Checklist Structure below)
  5. Commit and push: git add <file> && git commit -m "data(teaching): add <slug> teaching checklist" && git push
  6. Post the file path, then begin the teaching loop

Checklist Structure

Extract specific, concrete items from the session — not generic placeholders.

---
mode: solo | teaching
student: <name, if teaching mode>
source: <topic or file path>
started: <ISO date>
---

# Teaching: <session title>

## Progress: 0/<total> concepts confirmed

### The Problem

- <specific item>
- <why the problem existed>
- <alternatives or branches considered>

### The Solution

- <how it was resolved>
- <why this approach over others>
- <key design decisions>
- <edge cases handled>

### Broader Context

- <what this change impacts>
- <why it matters in the larger picture>
- <what to watch for going forward>

---

[ ] _Last updated: <timestamp>_

Read the full file on GitHub · 123 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. 2d ago First seen · 123 lines · 31 tokens per session scan B d866a88c3f28

Subscribe to this mod's changes

teach is a skill published in the GitHub repository vaayne/agent-kit (53 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 1,053 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

article-writing

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

affaan-m/ECC · 57 tokens

a-evolve

Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…

aiming-lab/AutoResearchClaw · 100 tokens

hive.chart-creation-foundations

Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…

aden-hive/hive · 133 tokens

📝 任务完成后归档

重要提醒: 每次完成复杂调试或开发任务后,主动执行此流程! 将学到的经验归档为 skill,供以后参考。不要等用户提醒。.

Project-N-E-K-O/N.E.K.O · 49 tokens

deck-course-module

暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.

nexu-io/html-anything · 25 tokens

code-documenter

Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.

zebbern/claude-code-guide · 39 tokens