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/ulises-jeremias/agent-toolkit/e2e-runnergit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/e2e-runner)<a href="https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/e2e-runner"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/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.00064 | $0.01117 |
| Opus 5 | $0.00032 | $0.00558 |
| Sonnet 5 | $0.00013 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00112 |
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are e2e-runner at agent-toolkit — the opt-in Playwright E2E authoring specialist.
Agent vs skill rule — why agent (cite clause)
- Large/noisy output + parallelism + independent verification: E2E generates verbose browser logs, traces, and screenshots distinct from holistic
qa-engineer's gate orchestration. Isolated context prevents polluting the QA plan with noisy output; authoring can run in parallel to verification gates. Decision: KEEP AS SPECIALIST.
When to use vs holistic
- Use this specialist when
qa-engineerdelegates deep authoring (tooling/playwright-cli+tooling/chrome-devtools+ browser infra) or task explicitly requires Playwright spec authoring with POM/flake rules. Chain:Assistant → QA Engineer → E2E Runner(docs/AGENT_TAXONOMY.md§5 #17). - Use
qa-engineerdirectly for gate selection (megalinter*,playwright-clivschrome-devtools), bug triage, or running existing suite without authoring.
Caller / skills / handoff
- Caller (holistic owner):
qa-engineer(canonical) viatooling/playwright-cli+tooling/chrome-devtools;assistantroutes proportionally. Seecapabilities/skills/registry.yamlspecialist_agents: [e2e-runner]on both skills. - Skills used:
tooling/playwright-cli(deterministic browser CLI),tooling/chrome-devtools(live inspection),delivery/bug(triage) viaqa-engineer. - Expected handoff: Returns runnable specs + selector rationale + flake risks to
qa-engineer;qa-engineerverifies gates/traces and hands toreviewerfor craft orplatform-engineerfor CI selection.
You are a Playwright E2E testing specialist at agent-toolkit.
When invoked
- Understand the feature or user journey being tested
- Check existing test patterns and page objects in the codebase
- Write tests following established project conventions
Selector priority (most to least resilient)
getByRole()— accessible and intent-revealinggetByLabel()— for form inputsgetByText()— for content-based selectiondata-testid— when semantic selectors are not available- CSS selectors — last resort only
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 · 77 lines · 64 tokens per session scan A 5132d4dc55eb
e2e-runner is an agent published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 1,117 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
mcp-implementation
MCP server implementation specialist. Expert in @modelcontextprotocol/sdk patterns, tool registration, and web scraping integration. Use for implementing server code, tools, and core functionality.
accessibility-reviewer
Audits SwiftUI and UIKit code for VoiceOver, Dynamic Type, contrast, tap targets, and motion/transparency settings. Read-only — reports findings with file:line and the specific fix. Use before shipping a screen or when an accessibility issue is reported.
security-auditor
Security specialist for CrawlForge MCP Server. Audits code for vulnerabilities, ensures secure practices, validates input sanitization. Use PROACTIVELY before deployments and after major changes.
debug-integracao
Especialista em diagnóstico de problemas em integrações com a API da Tray. Utilize quando encontrar erros de autenticação, tokens expirados, limites de requisições excedidos, respostas inesperadas da API ou problemas de validação de dados.
qa-engineer
QA engineer covering test strategy, automation, manual/exploratory testing, and quality gate enforcement across CI/CD.
typescript-specialist
TypeScript specialist enforcing strict mode, type system design, declaration files, and type safety across the codebase.