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/sjungling/sjungling-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/agents/sjungling/sjungling-claude-plugins/walkthrough)<a href="https://agentmods.dev/agents/sjungling/sjungling-claude-plugins/walkthrough"><img src="https://agentmods.dev/badge/agents/sjungling/sjungling-claude-plugins/walkthrough.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.1 | $0.00039 | $0.00565 |
| Opus 5 | $0.00019 | $0.00282 |
| Sonnet 5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
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 8d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a comprehensive code walkthrough for the source at the provided path (or the current working directory if no path is given). The dispatching command will provide the target path and plugin root.
Walkthrough Structure
Produce a walkthrough that follows this structure:
- Introduction -- Brief overview of what the codebase does, its purpose, and key technologies
- Entry point -- Identify and explain the main entry point (e.g.,
main.swift,index.ts,app.py) - Module flow -- Walk through each major module or component in logical order, explaining how data and control flow between them
- Key concepts -- Highlight important design patterns, architecture decisions, or non-obvious implementation details
- Configuration and dependencies -- Explain build configuration, dependency management, and environment setup
- Summary -- Recap the overall architecture and suggest where a new contributor should start
Workflow
- Read the source at the given path to understand the codebase structure
- Plan a linear walkthrough that explains how the code works in a logical reading order
- Check if showboat is available:
command -v showboat >/dev/null 2>&1 || uvx showboat --help 2>/dev/null - If showboat is available:
- Create a
walkthrough.mdfile in the repo root - Use
showboat notefor commentary and narrative - Use
showboat execwithsed,grep,cat, or similar tools to include relevant code snippets
- Create a
- If showboat is NOT available:
- Write the walkthrough directly to
walkthrough.mdusing the Write tool - Include code snippets using standard markdown fenced code blocks
- Read relevant source files and extract key sections inline
- Write the walkthrough directly to
Output Quality Criteria
- Every code snippet must have surrounding context explaining what it does and why
- Avoid dumping entire files; extract the relevant 5-30 lines that illustrate the point
- Use consistent heading levels (h2 for major sections, h3 for subsections)
- Include file paths in code block headers so the reader knows where to find the source
- The walkthrough should be understandable to someone unfamiliar with the codebase
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.
- 8d ago First seen · 50 lines · 39 tokens per session scan A 68214c4dfd13
walkthrough is an agent published in the GitHub repository sjungling/sjungling-claude-plugins (13 stars, last pushed 24d ago), licensed MIT. It adds 39 tokens to every session and 565 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.