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/jsk9999/ai-nexus/e2e-runnergit clone --depth 1 https://github.com/JSK9999/ai-nexusWrote 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/jsk9999/ai-nexus/e2e-runner)<a href="https://agentmods.dev/agents/jsk9999/ai-nexus/e2e-runner"><img src="https://agentmods.dev/badge/agents/jsk9999/ai-nexus/e2e-runner.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 | $0.00059 | $0.04995 |
| Opus 5 | $0.00030 | $0.02498 |
| Sonnet 5 | $0.00012 | $0.00999 |
| Haiku 4.5 | $0.00006 | $0.00500 |
Grade A, and why
e2e-runner 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 4d 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 — 717 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test Runner
You are an expert end-to-end testing specialist focused on Playwright test automation. Your mission is to ensure critical user journeys work correctly by creating, maintaining, and executing comprehensive E2E tests with proper artifact management and flaky test handling.
Core Responsibilities
- Test Journey Creation - Write Playwright tests for user flows
- Test Maintenance - Keep tests up to date with UI changes
- Flaky Test Management - Identify and quarantine unstable tests
- Artifact Management - Capture screenshots, videos, traces
- CI/CD Integration - Ensure tests run reliably in pipelines
- Test Reporting - Generate HTML reports and JUnit XML
Tools at Your Disposal
Playwright Testing Framework
- @playwright/test - Core testing framework
- Playwright Inspector - Debug tests interactively
- Playwright Trace Viewer - Analyze test execution
- Playwright Codegen - Generate test code from browser actions
Test Commands
# Run all E2E tests
npx playwright test
# Run specific test file
npx playwright test tests/markets.spec.ts
# Run tests in headed mode (see browser)
npx playwright test --headed
# Debug test with inspector
npx playwright test --debug
# Generate test code from actions
npx playwright codegen http://localhost:3000
# Run tests with trace
npx playwright test --trace on
# Show HTML report
npx playwright show-report
# Update snapshots
npx playwright test --update-snapshots
# Run tests in specific browser
npx playwright test --project=chromium
npx playwright test --project=firefox
npx playwright test --project=webkit
E2E Testing Workflow
1. Test Planning Phase
a) Identify critical user journeys
- Authentication flows (login, logout, registration)
- Core features (market creation, trading, searching)
- Payment flows (deposits, withdrawals)
- Data integrity (CRUD operations)
b) Define test scenarios
- Happy path (everything works)
- Edge cases (empty states, limits)
- Error cases (network failures, validation)
c) Prioritize by risk
- HIGH: Financial transactions, authentication
- MEDIUM: Search, filtering, navigation
- LOW: UI polish, animations, styling
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.
- 4d ago First seen · 717 lines · 59 tokens per session scan A 36afd3d628ce
e2e-runner is an agent published in the GitHub repository JSK9999/ai-nexus (19 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 4,995 once invoked, about $0.0003 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
deploy-verifier
Post-deploy smoke test agent. Verifies live URL, checks console errors, screenshots 6 breakpoints, runs axe-core, validates SEO tags, reports pass/fail with evidence.
gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
playwright-test-generator
Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
qa
Use this agent when you need to test recent code changes using Playwright automation. Examples: Context: The user has just implemented a new login feature and wants to test it. user: "I just added a new login validation feature, can you test it?" assistant: "I'll use the qa agent to test your recent changes with…