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/kitlangton/skills/code-walkthroughnpx skills add kitlangton/skills --skill code-walkthroughgit clone --depth 1 https://github.com/kitlangton/skillsWhat 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.00057 | $0.01330 |
| Opus 5 | $0.00028 | $0.00665 |
| Sonnet 5 | $0.00011 | $0.00266 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
code-walkthrough 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 2d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Walkthrough
Use a verified tour: establish the real code and output first, then guide attention through one immutable Navi tour.
Prepare The Session
-
Confirm
termctrl, Neovim 0.10 or newer, andnavi.nvimare available. -
Start Neovim in the project root as a visible foreground session:
termctrl run walkthrough -- nvim -
Use Terminal Control from another process to inspect and drive that same session. Prefer
interactthrough the Terminal Control MCP when available; otherwise usetermctrl show,termctrl send, andtermctrl wait. -
Resize before composing the tour if the visible terminal is too narrow. Keep the size stable while presenting or recording.
The session is ready when the human and agent see the same settled Neovim screen and the agent can inspect it through Terminal Control.
Establish The Journey
- Ask what the viewer should understand or be able to explain afterward when the outcome is unclear.
- Read the relevant code and run the narrowest command that proves its current behavior.
- Inspect the actual visible result. Do not write notes from an expected or remembered result.
- Choose one conceptual journey. A useful journey often moves from public behavior to the mechanism that produces it, then to the observed result.
Do not combine an overview, failure diagnosis, implementation tour, and fix into one sequence. The journey is established when each planned stop is necessary to answer one coherent question.
Author One Immutable Tour
Create a JSON file outside the source tree when the tour is temporary. Use literal patterns when they are unique and stable; use line numbers only when exact positions are the point.
[
{
"file": "src/example.test.ts",
"pattern": "it(\"updates subscribers\"",
"end_pattern": "expect(runs).toBe(2)",
"message": "The public contract starts here: one write must cause one additional run."
},
{
"file": "src/example.ts",
"pattern": "export function notify",
"end_pattern": "subscriber()",
"message": "The implementation reaches every subscriber through this loop."
}
]
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.
- 2d ago First seen · 141 lines · 57 tokens per session scan A eadd4b5c44d6
code-walkthrough is a skill published in the GitHub repository kitlangton/skills (316 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 1,330 once invoked, about $0.0003 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-30.
Other skills, from other repositories
edu-math-tutorial
数学题分步讲解视频的领域知识。适用场景：(1) 用户给出一道数学题并要求做讲解/ 解题视频；(2) 用户说"讲解这道题"、"生成解题视频"、"make a math tutorial"； (3) 需要中文数学教学视频，涉及方程、公式或几何图形。本 skill 只提供领域 知识（题目拆解、讲解节奏、旁白文案规范、版式与 KaTeX 排版风格）；画面、 配音与成片一律用 Creator 原生 Element 与工具从源头构建。.
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…
coding-tutor
Personalized coding tutorials that build on your existing knowledge and use your actual codebase for examples. Creates a persistent learning trail that compounds over time using the power of AI, spaced repetition and quizes.
scholar-evaluation
Provide qualitative-first, evidence-traceable developmental review of scholarly works and audit low-stakes research-assessment rubrics with optional local quality controls. Never use for ranking people or consequential decisions.
practice-cognition
触发：当你提出了方案、假设或判断，需要通过实践验证、试错迭代或复盘升级认知时调用；常见信号包括 experiment、prototype、validate、iterate、feedback loop。 English: Trigger when an idea, hypothesis, or plan must be tested in practice and improved through iteration. Use this skill to move from action to understanding and back to action in a spiral learning loop.
offensive-exploit-dev-course
Full exploit development course roadmap and syllabus: weekly topics, recommended reading, lab setup, and learning path from vulnerability classes through advanced exploitation. Use to structure exploit dev training or onboard new researchers.