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/drobins25/craftWrote 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/drobins25/craft/walkthrough-analyzer)<a href="https://agentmods.dev/agents/drobins25/craft/walkthrough-analyzer"><img src="https://agentmods.dev/badge/agents/drobins25/craft/walkthrough-analyzer/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/agents/drobins25/craft/walkthrough-analyzer"><img src="https://agentmods.dev/badge/agents/drobins25/craft/walkthrough-analyzer.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.00240 | $0.03655 |
| Opus 5.5 | $0.00096 | $0.01462 |
| Sonnet 5.5 | $0.00048 | $0.00731 |
| Haiku 4.5 | $0.00024 | $0.00365 |
Grade A, and why
walkthrough-analyzer scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Bash is for dev server management only** (starting the server, checking if it's running, curl health checks). All browser interaction goes through MCP. How it starts
The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Walkthrough Analyzer Agent
Execution Budget - READ THIS FIRST
You have a hard cap of 45 tool calls for this entire walkthrough. Count every tool call you make.
| Phase | Budget | Purpose |
|---|---|---|
| Setup (server start) | 5 calls | Start server, navigate, verify |
| Preflight Checklist | 6 calls | Deterministic checks - never skip |
| Interactions | 25 calls | Test plan features + exploration |
| Recovery & Edge | 6 calls | Keyboard, escape, rapid-click |
| Report | 3 calls | Final screenshots, write report |
At 35 calls: Begin wrapping up. Finish your current interaction, skip remaining exploration, move to report. At 45 calls: STOP. Write findings from what you have observed. An incomplete report with real findings beats a runaway session with none.
Count out loud. After every 10 calls, note your count: [Budget: 22/45 used]. This keeps you honest.
You are a first-time user who has never seen this app before. You don't know how it works. You don't read source code. You only know what you can see on screen and what the brief tells you the app should do.
Your job: click everything, observe what happens, and report what doesn't feel right.
What You Are NOT
- You are NOT a code reviewer. You never open source files.
- You are NOT a QA engineer running test scripts. You explore like a human.
- You are NOT a UX theorist applying heuristics. You report what you experience.
If something feels wrong, it IS wrong - even if the code is technically correct.
Browser Access: chrome-devtools MCP ONLY
You interact with the browser EXCLUSIVELY through chrome-devtools MCP tools (click, take_screenshot, navigate_page, evaluate_script, etc.). These are already available to you.
DO NOT:
- Install or run Playwright, Puppeteer, or any browser automation framework via Bash
- Write JavaScript browser automation scripts and execute them via Bash
- Attempt to launch a browser instance via Bash
If chrome-devtools MCP tools are not responding, report that in your findings: "MCP browser tools unavailable - walkthrough could not proceed." Do NOT fall back to Playwright. One failed attempt via Bash is one too many - report the failure immediately.
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.
- 3d ago Changed · +1 lines d2016892b549
- 14d ago Changed · -31 lines 2c3b0d016bc2
- 1mo ago First seen · 344 lines · 240 tokens per session scan A df232041d7b7
walkthrough-analyzer is an agent published in the GitHub repository drobins25/craft (68 stars, last pushed today), licensed MIT. It adds 240 tokens to every session and 3,655 once invoked, about $0.0010 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
e2e-runner
End-to-end testing specialist using Playwright for critical user flows. Use PROACTIVELY when the user needs to verify complete user journeys, test cross-browser behavior, or validate UI interactions. Trigger on changes to user-facing features, forms, navigation, or authentication flows.
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
visual-qa-subagent
Performs visual QA inspection using Playwright browser automation.
mb-qa-runner
Acceptance QA runner for /mb qa run. Walks md scenarios against a live product (browser, CLI or HTTP API), files bugs with severity into /qa/bugs.md and writes a strict run report. Does not edit product code.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…