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/lingochunk/mcp/lingochunk-coursenpx skills add lingochunk/mcp --skill lingochunk-coursegit clone --depth 1 https://github.com/lingochunk/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/lingochunk/mcp/lingochunk-course)<a href="https://agentmods.dev/skills/lingochunk/mcp/lingochunk-course"><img src="https://agentmods.dev/badge/skills/lingochunk/mcp/lingochunk-course.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.00092 | $0.01422 |
| Opus 5 | $0.00046 | $0.00711 |
| Sonnet 5 | $0.00018 | $0.00284 |
| Haiku 4.5 | $0.00009 | $0.00142 |
Grade A, and why
lingochunk-course 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 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.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LingoChunk course planner
Turn one rich episode (or a collection) into a coherent SERIES of lessons: a
named course with N ordered lessons, each a self-contained lingochunk-lesson
document with a DIFFERENT grammar point and a difficulty that ramps across the
series. LingoChunk supplies the materials (transcripts with positions and
translations, FSRS-graded vocabulary) and renders every lesson natively; your
job is the arc - how to slice the source, what each lesson teaches, and in what
order - and then to drive the existing lesson flow once per slice.
This skill uses the lingochunk MCP tools. If they are not available, tell the
user to add the LingoChunk MCP server (see the plugin README) and stop. This
skill ORCHESTRATES lingochunk-lesson: read that guide (get_authoring_guide
with topic='lesson') before composing any single lesson - this one only adds
the multi-lesson planning on top.
When to use
- "Make a course out of this episode."
- "Build me a series of lessons on the B1 podcast, one per scene."
- "Break this 20-minute episode into a study plan I can work through."
- "Turn this collection into a beginner course."
Options to settle first (ask only what the user left open)
- Source: one episode (
list_library), or a collection you slice episode by episode. A single lesson has ONE source episode in v1, so each lesson in the course draws from one episode (or one slice of it). - Length: how many lessons. Default to what the material honestly supports - a 3-8 minute slice per lesson, so a 20-minute episode is ~3-5 lessons, not fifteen thin ones. Say the number you chose and why.
- Level and ramp: the starting CEFR level and whether it climbs. Infer
the floor from the CEFR mix of
get_vocabulary(status=known)if the user does not say. State the ramp (e.g. "A2 for lessons 1-2, B1 for 3-4").
Workflow
- Inventory the source.
list_libraryto find the episode(s). For each, pull the shape:get_transcript(sentence positions, timings, speakers) andget_vocabulary(what is known vs learning/new/due). You are looking for natural seams - scene changes, topic shifts, a run of sentences that share a grammar pattern - and for which grammar points the material can actually evidence. - Split into coherent slices. Carve the source into N slices, each a
3-8 minute span that stands on its own AND carries enough evidence for one
grammar point. Prefer seams the audio already has (a new scene, a new
speaker turn) over arbitrary time cuts. Write down, per slice: its
from_time/to_time, its ONE grammar point, its level, and 2-3 archetypes from the lesson skill's menu - deliberately varying the archetype mix across slices so consecutive lessons do not feel identical. - Ramp the difficulty. Order the slices so difficulty climbs: earlier lessons lean on recognition (MCQ, matching, sentence reorder) and lower-level grammar; later lessons lean on recall and production (dictation, shadowing, gap-fill, production) and harder points. No grammar point repeats across the course - depth over coverage, one point per lesson, a different point each lesson.
- Create the course.
create_coursewith atitleand a shortdescriptionnaming the arc. Keep itsid. - Build the lessons in order. For each slice, run the full
lingochunk-lessonflow (pull the slice, filter vocabulary, pick the ONE grammar point you assigned it, compose on the scaffold with its archetypes). Before each save, callvalidate_lessonwith{document}and fix EVERY problem it reports; only once it returnsvalid: truedo yousave_lessonwith{document, course_id, sequence}-sequence= the lesson's 1-based position in the course (ties break by created_at, but pass explicit sequences so the order is deliberate). Stampgenerator: {skill: "lingochunk-lesson"}on each document. - Deliver. List the course and its lessons in order (title, level, grammar
point,
app_url), so the user can work through them as a series. Offeradd_cardfor the drill words the course introduced. Confirm the course groups them:list_lessonsechoes each lesson'scourse_id,sequenceandcourse_title.
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 · 96 lines · 92 tokens per session scan A c1de8cc71876
lingochunk-course is a skill published in the GitHub repository lingochunk/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,422 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-08-31.
Other skills, from other repositories
anki
Use when the user wants to create Anki flashcards, manage Anki decks, search notes, or interact with Anki via AnkiConnect. Triggers on phrases like "create flashcards", "add to Anki", "make Anki cards", "batch create notes", or "manage my Anki deck".
language-coach
Use when the user asks how to say something in another language, wants to express an idea in a foreign language, asks about phrasing or wording in any non-English language, or asks how to pronounce something. Trigger phrases include "how do I say", "how would a native speaker say", "what's the right way to say", "how…
aha
Explain an expression in the language you're learning that you can't read literally — get a verdict (memorize vs learnable rule) + how to read it, saved to the decode dataset. Usage: /aha [+ your hunch].
tutor
Drill your recorded pains (friction phrasings, grammar fixes, irregular verbs, learned vocab) with spaced repetition. Usage: /tutor [size].
vozclara-pack-from-url
Turn a YouTube URL into a structured Knowledge Pack via VozClara — summary, key ideas, glossary, vocabulary, citations, in the user's language. No sign-up needed for one-off use.
vibeue
Unreal Engine 5 development using the VibeUE Python API. Use when working in Unreal Engine — blueprints, state trees, materials, actors, landscapes, animation, niagara, widgets, sound, foliage, gameplay tags, enhanced input, skeletons, PCG (procedural content generation), and more. VibeUE is an extension of Unreal's…