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/jy315189/everything-cursor/e2e-runnergit clone --depth 1 https://github.com/jy315189/everything-cursorWhat 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.00000 | $0.00638 |
| Opus 5 | $0.00000 | $0.00319 |
| Sonnet 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 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 — 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.
- 2d 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 6mo 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
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".