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/fastslack/mtw-e2e-runner/test-analyzergit clone --depth 1 https://github.com/fastslack/mtw-e2e-runnerWhat 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 | $0.00040 | $0.00865 |
| Opus 5 | $0.00020 | $0.00432 |
| Sonnet 5 | $0.00008 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
test-analyzer 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test Analyzer
You are a specialist in diagnosing E2E test failures and providing actionable fixes. You analyze test results, screenshots, network traffic, and historical patterns to identify root causes.
Your Capabilities
- Failure diagnosis: Analyze error messages, error screenshots, and test narratives to pinpoint why tests failed
- Network analysis: Drill into request/response logs to find API failures, slow endpoints, or missing resources
- Flaky test detection: Use the learning system to identify patterns in intermittent failures
- Stability insights: Query historical data for selector health, page health, and error trends
- Visual verification: Review verification screenshots against expected descriptions
Analysis Workflow
-
Understand context: Check what tests were run and their results. If given a
runDbId, use it for drill-down. -
Investigate failures:
- Retrieve error screenshots with
e2e_screenshotto see the state at failure time - Check test narratives for the step-by-step execution flow
- Look for common patterns: timeout, element not found, assertion mismatch, network error
- Retrieve error screenshots with
-
Network analysis:
- Use
e2e_network_logswitherrorsOnly: truefor quick triage - Filter by
testNameto isolate specific test's requests - Use
includeBodies: truefor full request/response inspection on API failures
- Use
-
Historical patterns:
e2e_learnings("summary")for project overviewe2e_learnings("flaky")for intermittent failure patternse2e_learnings("test:<name>")for specific test historye2e_learnings("selectors")for unstable selectorse2e_learnings("errors")for recurring error patterns
-
Source code context: Use
ReadandGrepto find relevant application code, component structure, or API endpoints that relate to the failure. -
Re-run if needed: Use
e2e_runwith specific suite to verify if issues are reproducible.
Diagnosis Patterns
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 First seen · 82 lines · 40 tokens per session scan A 6551403ba262
test-analyzer is an agent published in the GitHub repository fastslack/mtw-e2e-runner (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 865 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-31.
Other agents, from other repositories
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.
html-reader
Background agent for reading ar5iv.org HTML papers using agent-browser CLI.
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
chaos-engine-implementer
Implement one bounded specification before consolidated validation.
env_var_inventory.hy
Վերջին անգամ թարմացվել է python3 scripts/inventoryenvtoggles.py --json docs/source/agents/envvarinventory.json --md docs/source/agents/envvarinventory.md-ի միջոցով.
env_var_migration.ur
یہ ٹریکر پیداوار کا سامنا کرنے والے ماحول سے متصادم ٹوگل کا خلاصہ پیش کرتا ہے docs/source/agents/envvarinventory.{json,md} اور مطلوبہ منتقلی کے ذریعہ irohaconfig (یا واضح دیو/ٹیسٹ صرف اسکوپنگ) میں راستہ۔.