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 agentmods add agents/multiplex-ai/muggle-ai-works/visual-walkthrough-buildergit clone --depth 1 https://github.com/multiplex-ai/muggle-ai-worksWrote 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/multiplex-ai/muggle-ai-works/visual-walkthrough-builder)<a href="https://agentmods.dev/agents/multiplex-ai/muggle-ai-works/visual-walkthrough-builder"><img src="https://agentmods.dev/badge/agents/multiplex-ai/muggle-ai-works/visual-walkthrough-builder.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.00092 | $0.01080 |
| Opus 5 | $0.00046 | $0.00540 |
| Sonnet 5 | $0.00018 | $0.00216 |
| Haiku 4.5 | $0.00009 | $0.00108 |
Grade A, and why
visual-walkthrough-builder 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 5d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 5d ago First seen · 66 lines · 92 tokens per session scan A bedd269af971
visual-walkthrough-builder is an agent published in the GitHub repository multiplex-ai/muggle-ai-works (17 stars, last pushed today), with no licence file. It adds 92 tokens to every session and 1,080 once invoked, about $0.0005 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
auth-tester
Specialized agent for comprehensive authentication and login flow testing based on login constitutions.
e2e-tester
Tests web applications end-to-end using Glance browser MCP. Navigates pages, fills forms, clicks buttons, takes screenshots, runs assertions, and reports bugs. Use when you want to verify an app works correctly — login flows, forms, navigation, responsiveness — with real browser interaction.
browser-recorder
Record browser interactions and generate test definitions. Use when: (1) By feature-verify skill after exploration to generate test YAML, (2) By test-authoring skill for assisted test creation, (3) By user for "record this flow" requests.
pr-verifier
Single agent that verifies all PR frontend changes. Use when: (1) verify-pr command is invoked, (2) Complete PR verification with visual report is needed, (3) Running verification in background while user continues working.
test-analyzer
Deep analysis of E2E test failures and results. Use when: (1) A test has failed and needs root cause analysis, (2) User wants to understand why a step failed, (3) Complex multi-step failures need investigation.
test-creator
Use this agent to create new E2E tests by exploring the application UI, analyzing source code, and designing test actions. Best used when you need to write tests for a new feature, page, or user flow.