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/multiplex-ai/muggle-ai-teamsWrote 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/commands/multiplex-ai/muggle-ai-teams/e2e)<a href="https://agentmods.dev/commands/multiplex-ai/muggle-ai-teams/e2e"><img src="https://agentmods.dev/badge/commands/multiplex-ai/muggle-ai-teams/e2e/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/commands/multiplex-ai/muggle-ai-teams/e2e"><img src="https://agentmods.dev/badge/commands/multiplex-ai/muggle-ai-teams/e2e.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.00028 | $0.02495 |
| Opus 5.5 | $0.00011 | $0.00998 |
| Sonnet 5.5 | $0.00006 | $0.00499 |
| Haiku 4.5 | $0.00003 | $0.00249 |
Grade A, and why
e2e 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 1mo 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.
This is a copy
84% identical to e2e — 246 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Command
This command invokes the e2e-runner agent to generate, maintain, and execute end-to-end tests using Playwright.
What This Command Does
- Generate Test Journeys - Create Playwright tests for user flows
- Run E2E Tests - Execute tests across browsers
- Capture Artifacts - Screenshots, videos, traces on failures
- Upload Results - HTML reports and JUnit XML
- Identify Flaky Tests - Quarantine unstable tests
When to Use
Use /e2e when:
- Testing critical user journeys (login, trading, payments)
- Verifying multi-step flows work end-to-end
- Testing UI interactions and navigation
- Validating integration between frontend and backend
- Preparing for production deployment
How It Works
The e2e-runner agent will:
- Analyze user flow and identify test scenarios
- Generate Playwright test using Page Object Model pattern
- Run tests across multiple browsers (Chrome, Firefox, Safari)
- Capture failures with screenshots, videos, and traces
- Generate report with results and artifacts
- Identify flaky tests and recommend fixes
Example Usage
User: /e2e Test the market search and view flow
Agent (e2e-runner):
# E2E Test Generation: Market Search and View Flow
## Test Scenario Identified
**User Journey:** Market Search → View Results → Click Market → View Details
**Test Coverage:**
1. Navigate to markets page
2. Perform semantic search
3. Verify search results
4. Click on first result
5. Verify market details page loads
6. Verify chart renders
## Generated Test Code
```typescript
// tests/e2e/markets/search-and-view.spec.ts
import { test, expect } from '@playwright/test'
import { MarketsPage } from '../../pages/MarketsPage'
import { MarketDetailsPage } from '../../pages/MarketDetailsPage'
test.describe('Market Search and View Flow', () => {
test('user can search markets and view details', async ({ page }) => {
// 1. Navigate to markets page
const marketsPage = new MarketsPage(page)
await marketsPage.goto()
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.
- 1mo ago First seen · 366 lines · 28 tokens per session scan A b1196cfc5ffc
e2e is a command published in the GitHub repository multiplex-ai/muggle-ai-teams (2 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 2,495 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to e2e, differing in 246 lines, and is treated as a copy.
Other commands, from other repositories
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
cover
Generate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after…
paul:verify
Guide manual user acceptance testing of recently built features.
spec-check
Audit GWT acceptance test specs for implementation leakage. Optionally provide a specific file path.
tea
Testing Autónomo End-to-End (TEA): genera, ejecuta y reporta tests automáticamente. Usa cuando el usuario dice "E2E test", "test end-to-end", "correr tests", "generar tests", "testing suite", "run tests", "automated testing", "pruebas E2E", "test coverage", "regression testing". Detecta el framework de testing del…