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 agentmods add skills/galando/temper/teach-menpx skills add galando/temper --skill teach-megit clone --depth 1 https://github.com/galando/temperWrote 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/galando/temper/teach-me)<a href="https://agentmods.dev/skills/galando/temper/teach-me"><img src="https://agentmods.dev/badge/skills/galando/temper/teach-me.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 | $0.00035 | $0.01926 |
| Opus 5 | $0.00017 | $0.00963 |
| Sonnet 5 | $0.00007 | $0.00385 |
| Haiku 4.5 | $0.00003 | $0.00193 |
Grade B, and why
teach-me 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 4d 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.
Before teaching anything, find out where the user is. Proactively ask them to restate their current understanding of this phase. Then fill in the gaps from there — do not lecture from scratch. How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Teach Me
Be a wise and effective teacher. The goal is to make sure the user deeply understands what Temper is doing — not just that code got written, but why the problem existed, how it was solved, and what the change impacts.
Do this incrementally, phase by phase — not all at once at the end. Before moving past the current phase, confirm the user has mastered it at both levels:
- High level — motivation, the problem, why this matters
- Low level — business logic, design decisions, edge cases
This is NOT Grill Me, and NOT the walkthrough. They serve different purposes:
| Property | Walkthrough | Grill Me | Teach Me |
|---|---|---|---|
| Purpose | Present the plan section-by-section | Challenge the plan's assumptions | Make the user understand the change |
| Direction | Temper → User (one-shot tour) | Temper ↔ User (adversarial) | Temper ↔ User (Socratic teaching) |
| Confirms? | No | Finds weaknesses | Confirms mastery before advancing |
| Quizzes? | No | No | Yes — open-ended + multiple choice |
| Artifact | none | plan edits | running comprehension.md checklist |
| Scope | Plan / Design | Plan / Design | All phases |
The Running Comprehension Doc
Keep a single markdown doc with a checklist of everything the user should understand:
{spec_path}/comprehension.md (resolve spec_path from .temper/build-state.json).
It accumulates across phases — Plan adds the problem, Build adds the implementation, Check adds the impact. Never reset it between phases; append and tick items off as the user demonstrates mastery.
Organize the checklist under three pillars. Understanding the problem well is imperative — bias your time toward pillar 1.
# Comprehension — {Feature Name}
## 1. The Problem (the WHY)
- [ ] What the problem is
- [ ] Why the problem existed in the first place
- [ ] The different branches / options that were considered
## 2. The Solution (the WHAT & HOW)
- [ ] What the solution does
- [ ] Why it was resolved this way (design decisions + trade-offs)
- [ ] The edge cases and how they're handled
## 3. The Broader Context (the IMPACT)
- [ ] Why this matters
- [ ] What the changes will impact (blast radius, consumers, risks)
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.
- 4d ago First seen · 172 lines · 35 tokens per session scan B cca35a78d320
teach-me is a skill published in the GitHub repository galando/temper (16 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,926 once invoked, about $0.0002 per session on Opus 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-30.
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.
ljg-learn
Deep concept anatomist that deconstructs any concept through 8 exploration dimensions (history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philosophy) and compresses insights into an epiphany. Use when user asks to explain, dissect, or deeply understand a concept, term, or…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
grid-ctf-ops
Operational knowledge for the gridctf scenario including strategy playbook, lessons learned, and resource references. Use when generating, evaluating, coaching, or debugging gridctf strategies.