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 skillmds/skillmd --skill code-walkthroughgit clone --depth 1 https://github.com/skillmds/skillmdWrote 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/skillmds/skillmd/code-walkthrough)<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.
<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>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.00057 | $0.01331 |
| Opus 5.5 | $0.00023 | $0.00532 |
| 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 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.
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.
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.
- 4d ago First seen · 141 lines · 57 tokens per session scan A 71bceef778ee
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.
Other skills, from other repositories
gws-classroom
Google Classroom: Manage classes, rosters, and coursework.
get-rep-call-feedback
Use when the user wants evidence-backed coaching for one rep's calls, especially by comparing the rep with peer examples to identify repeatable best practices, specific upgrade moments, and practical next-call language.
recipe-create-classroom-course
Create a Google Classroom course and invite students.
tutorial
Interactive tutorial teaching Ouroboros hands-on.
printing-press-retro
Use when the user asks to retro, run a retrospective, file findings, or improve the Printing Press after a printed-CLI run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings". Do not use for…
socratic-quiz
Use this when the user wants to deeply understand something through guided questioning. Trigger phrases include: "quiz me", "help me understand", "Socratic", "teach me", "walk me through with questions", "test my understanding", or when the user asks for an explanation and would benefit more from guided discovery than…