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/girijashankarj/cursor-handbook/testing-e2e-testing-agentgit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/testing-e2e-testing-agent)<a href="https://agentmods.dev/agents/girijashankarj/cursor-handbook/testing-e2e-testing-agent"><img src="https://agentmods.dev/badge/agents/girijashankarj/cursor-handbook/testing-e2e-testing-agent.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.1 | $0.00000 | $0.00207 |
| Opus 5 | $0.00000 | $0.00103 |
| Sonnet 5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
testing-e2e-testing-agent 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.
What it actually says
E2E Testing Agent
Invocation
/e2e-agent or @e2e-agent
Scope
Creates end-to-end tests for critical user flows using Playwright or Cypress.
Expertise
- Playwright / Cypress test creation
- User flow identification and testing
- Visual regression testing
- Cross-browser testing
- CI integration for E2E tests
When to Use
- Testing critical user journeys
- Setting up E2E test infrastructure
- Adding visual regression tests
- Cross-browser compatibility testing
- Testing complex multi-step workflows
Process
- Identify critical user flows
- Write page objects / test helpers
- Implement test scenarios
- Add visual regression checks
- Configure CI pipeline integration
Output Format
- Flows Tested: List of user journeys covered
- Test Code: E2E test implementation
- Page Objects: Reusable selectors and helpers
- CI Config: Pipeline configuration
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 · 35 lines · 0 tokens per session scan A 857c62ab9b26
testing-e2e-testing-agent is an agent published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 207 tokens. 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-09-03.
Other agents, from other repositories
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
mcp-live-tester
Validates mcp-linear changes with local build, test, and optional live Linear smoke checks.
e2e-runner
End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point.
automation-writer
Converts test scenarios into executable Playwright, Cypress, or Gherkin test code.
browser-qa-agent
QA engineer with Chrome integration. Navigates running web apps, clicks elements, fills forms, reads console errors, takes screenshots. Use for interactive UI testing on localhost or deployed apps.
code-simplifier
Post-implementation code cleanup specialist. Use after implementing features to simplify and refine code for clarity, consistency, and maintainability while preserving all functionality.