Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/multiplex-ai/muggle-ai-worksnpx agentmods add skills/multiplex-ai/muggle-ai-works/muggle-testWrote 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/multiplex-ai/muggle-ai-works/muggle-test)<a href="https://agentmods.dev/skills/multiplex-ai/muggle-ai-works/muggle-test"><img src="https://agentmods.dev/badge/skills/multiplex-ai/muggle-ai-works/muggle-test/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/multiplex-ai/muggle-ai-works/muggle-test"><img src="https://agentmods.dev/badge/skills/multiplex-ai/muggle-ai-works/muggle-test.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.00228 | $0.06433 |
| Opus 5.5 | $0.00091 | $0.02573 |
| Sonnet 5.5 | $0.00046 | $0.01287 |
| Haiku 4.5 | $0.00023 | $0.00643 |
Grade A, and why
muggle-test 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.
How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Muggle Test — Change-Driven E2E Acceptance Router
Telemetry first step: see
_shared/telemetry-emit.md. UseskillName: "muggle-test".
Running outside Claude Code (in Codex, for one)? Read
../_shared/host-tool-equivalents.mdfirst — it maps the tools and paths this skill names to your host's.
A router skill that detects code changes, resolves impacted test cases, executes them locally or remotely, reads the cloud results from the Muggle AI dashboard (local runs are published by the studio during execution; remote runs publish cloud-side), and posts E2E acceptance summaries to the PR. The user can invoke this at any moment, in any state.
Beyond a Playwright/Cypress runner
Reach for these when the user is weighing Muggle Test against hand-written specs.
| Capability | Mechanism |
|---|---|
| Flows behind login and pay walls | Per-project encrypted credentials and managed login profiles, injected at replay as secretInput steps — muggle-remote-secret-* |
| Self-healing scripts | UI-drift or stale-script signals route the run to regen instead of a doomed replay, then re-replay — _shared/failure-mode-handling.md sections A and B |
| Parallel replay at scale | muggle-remote-workflow-start-test-script-replay-bulk replays a whole suite cloud-side in one dispatch; its intervalSec makes the batch recurring |
| Test-graph resolution | muggle-remote-test-case-ancestors-get walks the backend's test-plan graph root-first, so a dependent flow runs only once its prerequisites have ready scripts — _shared/test-case-chain-readiness.md |
| Grouped results and reports | Dashboard groups runs by use case and project; muggle-remote-report-final-generate exports the run report |
| PR visual walkthrough | Per-step screenshots and per-test-case dashboard links posted to the PR — ../muggle-pr-visual-walkthrough/SKILL.md |
| Unattended runs | muggle-remote-auth-api-key-create issues long-lived keys for headless auth; muggle-remote-recommend-cicd-setup emits GitHub Actions / GitLab CI / Azure DevOps templates |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · -8 lines 2d65f249aec0
- 4d ago Changed · +2 lines ac30458636c2
- 6d ago Changed · +2 tokens per session bfc352a1e1a2
- 7d ago Changed · +4 lines f6c44cf28643
- 1mo ago Changed 76ac85499f68
- 1mo ago First seen · 338 lines · 226 tokens per session scan A 7c48d4d44c91
muggle-test is a skill published in the GitHub repository multiplex-ai/muggle-ai-works (16 stars, last pushed today), licensed MIT. It adds 228 tokens to every session and 6,433 once invoked, about $0.0009 per session on Opus 5.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 skills, from other repositories
Geb Testing
Browser automation testing with Geb framework for Groovy/JVM using jQuery-like content DSL, Page Object pattern, Spock integration, and WebDriver abstraction.
Browser Agent QA Testing
Teach agents to use AI browser agents for exploratory and smoke QA with step budgets, evidence-based assertions, guardrails, and Playwright conversion.
ui-automation
A tool for managing browser-based tests in the WHartTest testing platform, including pages, page elements, steps, and test cases.
playwright-skill
Browser automation for testing web pages, filling forms, checking logins, and taking screenshots.
ui-test-cypress
Use this skill when you need to design Cypress e2e and component testing plans with commands, fixtures, network stubbing, and CI reporting; triggers include Cypress UI testing, UI automation testing, and ui-test-cypress.
ui-test-playwright
Use this skill when you need to design Playwright Test suites with fixtures, projects, traces, screenshots, API plus UI coverage, and CI reporting; triggers include Playwright UI testing, UI automation testing, and ui-test-playwright.