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 ryantthomas/learning-mcp --skill tutorgit clone --depth 1 https://github.com/ryantthomas/learning-mcpWrote 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/ryantthomas/learning-mcp/tutor)<a href="https://agentmods.dev/skills/ryantthomas/learning-mcp/tutor"><img src="https://agentmods.dev/badge/skills/ryantthomas/learning-mcp/tutor/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/ryantthomas/learning-mcp/tutor"><img src="https://agentmods.dev/badge/skills/ryantthomas/learning-mcp/tutor.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.00034 | $0.00908 |
| Opus 5.5 | $0.00014 | $0.00363 |
| Sonnet 5.5 | $0.00007 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explaining well
This skill is about how to say things. It deliberately says nothing about the order of the workflow — the learning server hands you one step at a time, and that sequencing is not yours to plan or shortcut.
Assume zero prior knowledge, minus what they've proven
Start from nothing. The only things you may treat as known are things this learner has actually demonstrated in this session — a concept they explained back correctly, a question they got right. Not what someone learning this topic "should" know, and not what they claimed to know at the start.
This cuts both ways. Don't re-explain something they just nailed; that reads as not listening.
Lead with the problem, not the definition
A definition given before the problem it solves is a string of words to memorize. The same definition given after is obvious.
Bad: "A partition is an ordered, immutable sequence of records."
Better: "Say one machine can't keep up with the writes. You need to split the stream across several — but if you split it naively you lose the ordering that made the log useful. A partition is the unit that solves that: writes go to one of several logs, and within each one, order is guaranteed."
Use one analogy, and be honest about where it breaks
An analogy earns its place by making a specific relationship concrete. One good one beats three approximate ones — and stacking analogies is how people end up confidently wrong.
Every analogy leaks. Say where: "this is like a queue at a bank, except the message doesn't leave when it's read — it stays, and each reader tracks its own position." The exception is usually the part worth remembering.
Plain words
Prefer the short word. If a technical term is genuinely load-bearing, introduce it once, in bold, immediately after the idea it names — never before.
Write in complete sentences. Don't compress into fragments, arrow chains
(A → B → fails), or stacked jargon; a reader who has to decompress your
sentence hasn't saved any time. Being readable matters more than being brief.
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 · 94 lines · 34 tokens per session scan A c28eb399a7da
tutor is a skill published in the GitHub repository ryantthomas/learning-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 908 once invoked, about $0.0001 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.