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/endorhq/rover/update-e2e-testsgit clone --depth 1 https://github.com/endorhq/roverWhat 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.01391 |
| Opus 5 | $0.00000 | $0.00696 |
| Sonnet 5 | $0.00000 | $0.00278 |
| Haiku 4.5 | $0.00000 | $0.00139 |
Grade A, and why
update-e2e-tests 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update E2E tests
Update the existing end-to-end (e2e) tests across the entire project to match the specifications described in the E2E_TESTS.md files. The user also requests the following instructions: "$ARGUMENTS". Ignore if empty.
This command has four phases:
- Discover E2E specifications and existing tests
- Analyze gaps and inconsistencies
- Update tests
- Verify
You must complete all four phases in order.
Phase: Discover E2E specifications and existing tests
-
Find all
E2E_TESTS.mdfiles in the project by searching recursively from the project root. Read the root-leveldocs/E2E_TESTS.mdfirst to understand the overall testing philosophy, constraints, and execution methodology. -
For each
E2E_TESTS.mdfile found in a package directory, read it fully and extract:- All test suites listed
- For each suite: preconditions, features, and postconditions
- Any constraints on test ordering, isolation, or shared state
-
Find all existing e2e test files in the project. Look for:
- Files matching
**/*.e2e.test.ts - Files inside
**/e2e/**/*.test.tsdirectories - E2e-specific Vitest/Jest configuration files (e.g.,
vitest.e2e.config.ts)
- Files matching
-
Read all existing e2e test files fully to understand the current test coverage, patterns, helper utilities, and mocking strategies in use.
Phase: Analyze gaps and inconsistencies
For each package that has an E2E_TESTS.md file:
-
Map each test suite and feature described in
E2E_TESTS.mdto existing test files anddescribe/itblocks. Build a coverage matrix:- Which suites from the spec have corresponding test files?
- Which features within each suite have corresponding test cases?
- Which preconditions and postconditions are verified?
-
Identify:
- Missing suites: Test suites described in
E2E_TESTS.mdthat have no corresponding test file - Missing features: Features within a suite that have no corresponding test case
- Missing preconditions/postconditions: Setup or teardown that is described but not implemented
- Inconsistencies: Tests that exist but do not match the current spec (e.g., testing outdated behavior, wrong assertions, missing flags or options)
- Structural issues: Tests that violate the constraints from the root
docs/E2E_TESTS.md(e.g., tests that depend on execution order, share persistent state between suites)
- Missing suites: Test suites described in
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 · 108 lines · 0 tokens per session scan A 19d2ffcb482c
update-e2e-tests is a command published in the GitHub repository endorhq/rover (270 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,391 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-30.
Other commands, from other repositories
playwright
Write or update Playwright E2E tests following project conventions.
triage-ci
Triage E2E failures via local reruns or CI artifacts, classify flaky vs real-bug, present findings report.
implement
E2E-first Test driven development — unit tests written last.
e2e
Create and run E2E tests across web, mobile, and desktop with auto-detection and CLI-first toolchains.
frontend-e2e
Perform a thorough live E2E test of a frontend web application using browser-bridge MCP tools. Tests every page, interactive element, form, navigation flow, responsive breakpoint, and accessibility rule through real browser interaction.
health-check
Perform a comprehensive, read-only end-to-end review of any portfolio app across three layers — Frontend (E2E), Database integrity, and Audit Log & User Activity — and produce a structured, observations-only report. Optionally, on explicit opt-in, generate (never apply) the infrastructure provisions needed so future…