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 SimonSchick/code-tutor-narrator --skill skillgit clone --depth 1 https://github.com/SimonSchick/code-tutor-narratorWrote 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/simonschick/code-tutor-narrator/skill)<a href="https://agentmods.dev/skills/simonschick/code-tutor-narrator/skill"><img src="https://agentmods.dev/badge/skills/simonschick/code-tutor-narrator/skill/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/simonschick/code-tutor-narrator/skill"><img src="https://agentmods.dev/badge/skills/simonschick/code-tutor-narrator/skill.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.00066 | $0.00942 |
| Opus 5.5 | $0.00026 | $0.00377 |
| Sonnet 5.5 | $0.00013 | $0.00188 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
tutor 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 1mo 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tutoring out loud
You drive the user's editor while you talk. The tutor MCP server (from the
Code Tutor Narrator extension) gives you five tools:
show_code— scroll to a range, highlight it, dim the rest, speak the narration. Returns the numbered source lines, so you also read what you just pointed at.walkthrough— a planned sequence of beats, played back-to-back with no gaps.speak— say something without moving the editor.editor_state— active file, cursor, selection, visible lines, current errors.clear_highlight— drop the highlight, stop talking.
If a call fails with connection refused, VS Code isn't open — say so and stop trying; don't fall back to silently pasting code into chat.
A walkthrough that reports a timeout has not failed. It holds its response open
while the narration plays, so a long tour can outlive the MCP request window even
though the audio is still going. Never retry it and never re-narrate those beats —
you would talk over yourself. Carry on as if it succeeded; editor_state will show
which beat it reached.
How to run a session
Start where their attention already is. Call editor_state first. If they
have something selected or their cursor is parked somewhere, begin there rather
than at line 1.
Open with orientation, not code. One speak call saying what the file is for
and where you're going to take them. Two sentences.
Then move in beats. One idea per beat, 5–20 lines each. Never put a whole file into one beat.
Which tool depends on whether you already know what you're going to say:
walkthrough— hand it the planned beats and it plays them continuously, synthesising each while the previous is still speaking. Default to this for a section you've read and planned.show_code— one beat, blocking, returns the source. Use it when you need to read the code back before choosing the next beat, when the user is likely to interrupt, or when you're following their cursor.
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.
- 1mo ago First seen · 80 lines · 66 tokens per session scan A 2935cd6b732f
tutor is a skill published in the GitHub repository SimonSchick/code-tutor-narrator (0 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 942 once invoked, about $0.0003 per session on Opus 5.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
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
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.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.