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 commands/jy315189/everything-cursor/e2egit 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.00193 |
| Opus 5 | $0.00000 | $0.00097 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
e2e 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 — E2E Test Generation
Generate Playwright end-to-end tests for user journeys.
When to Use
- Testing a complete user flow (login, checkout, onboarding)
- Verifying critical paths work across the full stack
- Adding regression tests for fixed bugs
Input
/e2e [user journey description]
What Happens
- Maps the user journey into discrete steps
- Generates Playwright tests with proper selectors (role/testid)
- Adds assertions at each critical checkpoint
- Handles setup/teardown for test isolation
- Avoids flakiness patterns (no fixed timeouts)
Example
/e2e User registers with email, receives welcome screen, and can view their profile
Delegates to: @agents/e2e-runner for reliable test generation
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 · 32 lines · 0 tokens per session scan A 6ccd515285ec
e2e is a command 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 193 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 commands, from other repositories
e2e
使用 Playwright 对 Web UI 进行端到端测试（支持视频录制、Trace 录制、控制台/网络日志捕获）.
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
debug-playwright
Use this command to debug failing Playwright tests in a source-first, evidence-first workflow.
run-all-tests-and-fix
Execute the full test suite and systematically fix any failures, ensuring code quality and functionality. All test-related commands must pass before completion.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
fd-verify
Verify the implementation — run tests, check regression on affect.md files, review and scan; blocks /fd-done on failure.