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 tobihagemann/turbo --skill understand-changegit clone --depth 1 https://github.com/tobihagemann/turboWrote 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/tobihagemann/turbo/understand-change)<a href="https://agentmods.dev/skills/tobihagemann/turbo/understand-change"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/understand-change/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/tobihagemann/turbo/understand-change"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/understand-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00096 | $0.00953 |
| Opus 5 | $0.00048 | $0.00477 |
| Sonnet 5 | $0.00019 | $0.00191 |
| Haiku 4.5 | $0.00010 | $0.00095 |
Grade A, and why
understand-change 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 7d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Understand Change
Act as an effective teacher whose goal is the user's deep understanding of a change. Work incrementally, confirm mastery at each stage before advancing, and keep going until the user has demonstrated understanding of everything on the checklist.
Step 1: Identify the Change
Pick the subject in priority order:
- A commit, PR, or path passed as an argument — use that
- The work produced in the current session — use that
- Uncommitted work from
git statusandgit diff— use that - The most recent commit when nothing else is in scope
When the guess is not obvious, name what was picked so the user can redirect before teaching starts.
Step 2: Build the Understanding Checklist
Read the change in full: the diff, the touched files, related code, and any commit messages, plan, or PR description that explain intent.
Pick a slug for the change under study:
- Lowercase
- Replace non-alphanumeric characters with hyphens
- Collapse consecutive hyphens
- Trim leading and trailing hyphens
- Truncate to 40 characters at a word boundary
If the change is anchored to an existing plan at .turbo/plans/<slug>.md, reuse that plan's slug verbatim. If .turbo/understand/<slug>.md already exists, append -2, -3, etc. until the path is free. Do not overwrite: an existing checklist belongs to a session that may still be open.
The user may pass an explicit slug or output path; honor it. A path that already exists is background input naming the change to study, not a destination — treat it as the output path only when the request says so explicitly. When an explicit output path already exists, use AskUserQuestion to ask whether to overwrite, append a numeric suffix, or pick a different slug.
State the chosen path before continuing.
Write a running checklist to that path, with a checkbox per item, grouped into three sections:
- Problem — what the problem was, why it existed, and the alternative approaches that were on the table.
- Solution — what the change does, why it was resolved this way, the design decisions, and the edge cases.
- Context — why this matters and what the change impacts elsewhere.
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.
- 7d ago First seen · 60 lines · 96 tokens per session scan A b882f961c949
understand-change is a skill published in the GitHub repository tobihagemann/turbo (402 stars, last pushed 2d ago), licensed MIT. It adds 96 tokens to every session and 953 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
master
Turn reference docs into active mastery through retrieval practice, case binding, and scenario simulation. Combines Skycak (learning science) and Chin (expertise acceleration) frameworks. Use when you want to deeply learn material, not just read it.
upskilling-coach
Expert coach for learning, mastering, and upskilling in any domain. Use when the user wants to learn, master, improve, upskill, get better at, or get coached on any topic. Helps build consistent practice habits, identify prerequisites, design efficient learning loops, avoid common pitfalls, maintain discipline, and…
diffler
Generate and deliver a graded comprehension quiz from the current Git branch diff, either in the local terminal or through Google Forms. Use when a user asks to prove, test, or verify understanding of branch changes, a feature branch, or a pull request.
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
ape-quiz-me
Quizzes you on content you claim to have read -- Socratic, one question at a time, hints that narrow but never reveal. Ends with a verdict on what you understood versus merely recited. Trigger on "ape quiz me", "quiz me on this", "test my understanding", "did I actually get this", or any request to be tested on shared…
ape-write-pseudocode
Guidelines for writing pseudocode for functions and algorithms. Use this skill whenever the user asks to write pseudocode, sketch out an algorithm, or describe the logic of a function at a high level. Trigger on phrases like "write pseudocode", "sketch this algorithm", "pseudocode for this function", or "describe the…