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 atman-33/workhub --skill teach-backgit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/teach-back)<a href="https://agentmods.dev/skills/atman-33/workhub/teach-back"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/teach-back/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/atman-33/workhub/teach-back"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/teach-back.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.00000 | $0.01901 |
| Opus 5.5 | $0.00000 | $0.00760 |
| Sonnet 5.5 | $0.00000 | $0.00380 |
| Haiku 4.5 | $0.00000 | $0.00190 |
Grade A, and why
teach-back 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 14d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
teach-back
The user leaves able to explain the material in their own words. You get them there by asking, never by summarising: every answer on the record is theirs.
The measure is a teach-back — the user explaining the material back, as if to the person they will face. Your questions are the rehearsal for that person.
Armor mode
Material that makes causal claims or rests on hypotheses needs more than understanding: the user must be able to defend each claim. Armor mode adds steps 3, 7 and 8 below. It applies when the material asserts that A caused B, states a hypothesis, or is a report the user will stand behind. Plain reference material runs without it.
Armor means each claim is asserted at the strength its evidence supports. You cannot verify outside facts; the user's labels and their stated checks are the evidence. Say "I have not verified this" for whatever you could not check.
Steps
- Read the material. Files, folders, URLs, images and pasted text. Read pdf / pptx / xlsx / docx through their skills when installed; view images with Read. Done when you can point to where each claim in it lives.
- Ask for the audience. One question: who will they explain this to, what for, and who wrote the material (the user, an AI, someone else). The answer sets how deep to dig and which axes matter most; a user who wrote or is reporting the material owns its gaps. Done when you have a named listener, a purpose and a writer.
- Sort the claims (armor mode). List the material's claims, causal ones first, and have the user label each fact (observed: log, metric, repro, source), hypothesis (inferred) or unknown, naming where they checked it. Draw the cause-and-effect chain with those labels (references/diagrams.md). Done when every causal claim carries a label and a place it was checked.
- Map the questions (large or multi-file material only). Show 5–8 questions the user should be able to answer, most important first, and start from the one or two the rest stand on. Done when the user has seen the map.
- Get the first teach-back. Ask for the whole thing in three sentences, without jargon: what is this material and what does it say. Aim every later question at what this answer left thin.
- Question, one at a time. Pick from the axes below, in order of what matters for the stated audience. Loop until every mapped question — or, without a map, every axis that bears on the material — has a sound answer from the user or sits on the gap list.
- Settle each weak spot (armor mode). For every hypothesis, unknown and unsound answer, the user picks one: verify now (you offer the cheapest check), state as hypothesis (you offer wording such as "possible cause; confirming by X"), or leave out. Done when no weak spot is left without a choice.
- Cross-examine (armor mode). Play a sceptical listener and attack the chain one link at a time, using references/cross-examine.md. Include the questions the listener will most likely ask. Done when every link has survived an attack or has a settled choice from step 7.
- Close with recall. Ask for the teach-back again, now in full. Their words, not your summary.
- Hand over the record in chat (formats below). Save it to a file only when asked — to the path the user names, otherwise beside the material.
What ships with it
2 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.
- 14d ago Changed · +62 lines · -99 tokens per session fc59b58d49a4
- 26d ago First seen · 93 lines · 99 tokens per session scan A 6fc4039bee5b
teach-back is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,901 tokens. 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-09-20.
Other skills, from other repositories
academic-paper-workflow
Use when a user needs to plan, compose, or revise an academic paper in a staged workflow.
aetox-teach
สอนคนใช้ Aetox — ทำอะไรได้บ้างในคำที่คนเข้าใจ ห้องไหนไว้ทำอะไร ห้าอย่างที่คนใหม่ต้องรู้ และวิธีสอนด้วยการลงมือทำงานจริงของเขาแทนการบรรยาย · อ่านเมื่อผู้ใช้ถามว่าแอปนี้ทำอะไรได้ ถามวิธีใช้ หรือเพิ่งเปิดครั้งแรก.
interview-prep-generator
Generate STAR stories, practice questions, and talking points from resume.
async-learning-teacher
Transform saved links, papers, articles, posts, videos, and reference collections into approachable AI teaching artifacts for later study. Use when a user wants to queue learning material, create a readable explanation from a source, teach a paper or post step by step, or run an interactive tutor that validates…
digest
Generate a structured vibe-learn learning digest of the current coding session from .vibe-learn/session-log.jsonl.
readmd-style-custom
Generate custom CSS rules and HTML head tags for ReadMD document styling.