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.
git clone --depth 1 https://github.com/ApurvBazari/claude-pluginsWrote 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/plugins/apurvbazari/claude-plugins/walkthrough)<a href="https://agentmods.dev/plugins/apurvbazari/claude-plugins/walkthrough"><img src="https://agentmods.dev/badge/plugins/apurvbazari/claude-plugins/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/plugins/apurvbazari/claude-plugins/walkthrough"><img src="https://agentmods.dev/badge/plugins/apurvbazari/claude-plugins/walkthrough.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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.
What it actually says
{
"name": "walkthrough",
"version": "1.6.0",
"description": "Render a session or any subject (plugin, marketplace, path) as a self-contained interactive HTML document",
"author": { "name": "Apurv Bazari" },
"repository": "https://github.com/ApurvBazari/claude-plugins",
"license": "MIT",
"keywords": ["session-visualization", "interactive-html", "documentation", "diagrams", "system-map", "walkthrough", "session-recap", "cowork", "claude-cowork"]
}
What it installs
The manifest is a name and a version. 3 skills, 2 agents travel with it, and installing the plugin installs all of them — 435 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 Changed 9f2d450fc848
- 23d ago Changed 6b4099552cdc
- 1mo ago Changed 95de28bf37e7
- 1mo ago First seen · 10 lines scan A a8c353a77f44
walkthrough is a plugin published in the GitHub repository ApurvBazari/claude-plugins (1 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
ghostty-notify
Native Ghostty desktop notifications for Claude Code (idle input / permission request / turn finished) via OSC 777. Per-tab suppression and click-to-focus are handled natively by Ghostty. Runs only under Ghostty.
apple-pim
Native macOS integration for Calendar, Reminders, Contacts, and Mail using EventKit, Contacts, and JXA frameworks.
review-colleague-pr
Review a colleague's pull request carefully and considerately from a checkout of its branch, and report a brief, read-only assessment in chat: requirements, direction, blockers, follow-ups, and questions for the author.
write-formalization-roadmap
Document-structure guide for multi-milestone formalization roadmaps in Lean, Rocq, Isabelle, HOL, and other proof assistants.
plant-defects
Deliberately break code to prove a test can see it: plant the defect an instrument claims to catch, confirm it goes red, and record it so it regresses.
media
System-wide now-playing control for macOS — see and control whatever is playing (Spotify, Apple Music, browsers) right from Claude Code. Zero dependencies, no OAuth, no app lock-in.