code-walkthrough

code-walkthrough is a skill for Claude Code from skillmds/skillmd. It costs 57 tokens per session (1,331 once invoked), scanned A, a copy of code-walkthrough, MIT.

A guided method for presenting source code in Neovim, a terminal-based code editor, while showing verified output. It can also retain terminal evidence or record the walkthrough with OBS.

In plain words
What is it for?
Use it for live code tours, code-alongs, source explanations, and recorded terminal walkthroughs.
Why use it?
It prevents a code presentation from relying on guessed behavior or stale notes. The guide checks the real code and visible result before explaining it.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the agents-mcp plugin — 34 skills shipped together

Good fit Use it for live code tours, code-alongs, source explanations, and recorded terminal walkthroughs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/skillmds/skillmd/code-walkthrough
Install

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.

Any agent
npx skills add skillmds/skillmd --skill code-walkthrough
Clone the repo
git clone --depth 1 https://github.com/skillmds/skillmd

Made for: Claude Code.

Or install agents-mcp, the plugin that ships this one along with the rest of its 34 skills.

Wrote 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.

agentmods badge for code-walkthrough

README.md
[![agentmods](https://agentmods.dev/badge/skills/skillmds/skillmd/code-walkthrough/github.svg)](https://agentmods.dev/skills/skillmds/skillmd/code-walkthrough)
Your own site
<a href="https://agentmods.dev/skills/skillmds/skillmd/code-walkthrough"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/code-walkthrough/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.

agentmods 80×15 button for code-walkthrough

Your own site · 80×15
<a href="https://agentmods.dev/skills/skillmds/skillmd/code-walkthrough"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/code-walkthrough.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,331 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.01331
Opus 5.5 $0.00023 $0.00532
Sonnet 5 $0.00011 $0.00266
Haiku 4.5 $0.00006 $0.00133

Measured 4d ago against content hash 71bceef778ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-23, from the pricing page.

Security

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 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.

Origin

This is a copy

100% identical to code-walkthrough — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/agents-mcp/skills/code-walkthrough/SKILL.md · 141 lines

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

  1. Confirm termctrl, Neovim 0.10 or newer, and navi.nvim are available.

  2. Start Neovim in the project root as a visible foreground session:

    termctrl run walkthrough -- nvim
    
  3. Use Terminal Control from another process to inspect and drive that same session. Prefer interact through the Terminal Control MCP when available; otherwise use termctrl show, termctrl send, and termctrl wait.

  4. 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

  1. Ask what the viewer should understand or be able to explain afterward when the outcome is unclear.
  2. Read the relevant code and run the narrowest command that proves its current behavior.
  3. Inspect the actual visible result. Do not write notes from an expected or remembered result.
  4. 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."
  }
]

Read the full file on GitHub · 141 lines

Changes

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.

  1. 4d ago First seen · 141 lines · 57 tokens per session scan A 71bceef778ee

Subscribe to this mod's changes

code-walkthrough is a skill published in the GitHub repository skillmds/skillmd (1 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 1,331 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to code-walkthrough, differing in 2 lines, and is treated as a copy.