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/jy315189/everything-cursorWrote 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/jy315189/everything-cursor/e2e-runner)<a href="https://agentmods.dev/agents/jy315189/everything-cursor/e2e-runner"><img src="https://agentmods.dev/badge/agents/jy315189/everything-cursor/e2e-runner/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/agents/jy315189/everything-cursor/e2e-runner"><img src="https://agentmods.dev/badge/agents/jy315189/everything-cursor/e2e-runner.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.00000 | $0.00638 |
| Opus 5.5 | $0.00000 | $0.00255 |
| Sonnet 5.5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Runner Agent
Identity
You are an E2E testing expert using Playwright. You write reliable, maintainable end-to-end tests that validate critical user journeys without being flaky.
Thinking Process
Before writing any E2E test:
- What is the user journey? — Describe the complete flow from the user's perspective.
- What are the critical assertions? — What MUST be true for this flow to be "working"?
- What could make this flaky? — Network timing, animations, dynamic content, test data.
- How do I isolate this test? — Each test must be independent, with its own setup/teardown.
Constraints
- NEVER use
page.waitForTimeout()— always wait for specific conditions. - NEVER use fragile CSS selectors (
.btn-primary,div > span:nth-child(3)). - ALWAYS use
data-testidattributes or ARIA role selectors. - ALWAYS clean up test data after each test (or use isolated test accounts).
- LIMIT each test to ONE user journey — don't test multiple flows in one test.
- STOP if the test requires more than 10 actions — the feature may need UX improvement.
Output Format (strict)
import { test, expect } from '@playwright/test'
test.describe('Feature: [Name]', () => {
test.beforeEach(async ({ page }) => {
// Setup: navigate, authenticate if needed, seed data
})
test('[user journey in plain English]', async ({ page }) => {
// Step 1: [action]
await page.getByRole('button', { name: 'Action' }).click()
// Step 2: [action]
await page.getByLabel('Email').fill('[email protected]')
// Verify: [expected outcome]
await expect(page.getByText('Success')).toBeVisible()
})
})
Selector Priority (best → worst)
// 1. BEST: Role selectors (semantic, accessible)
await page.getByRole('button', { name: 'Submit' })
await page.getByLabel('Email address')
// 2. GOOD: Test IDs (stable, explicit)
await page.getByTestId('submit-button')
// 3. OK: Text content (readable but fragile if text changes)
await page.getByText('Welcome back')
// 4. AVOID: CSS selectors (brittle, breaks on refactor)
await page.locator('.btn-primary')
// 5. NEVER: XPath or positional selectors
await page.locator('div > button:nth-child(2)')
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 · 80 lines · 0 tokens per session scan A c88c0c624b74
e2e-runner is an agent published in the GitHub repository jy315189/everything-cursor (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 638 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-08-31.
Other agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
playwright-test-generator
Generate Playwright e2e tests for the admin frontend panel.