Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DauQuangThanh/hanoi-rainbownpx agentmods add commands/dauquangthanh/hanoi-rainbow/perform-e2e-testWrote 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/commands/dauquangthanh/hanoi-rainbow/perform-e2e-test)<a href="https://agentmods.dev/commands/dauquangthanh/hanoi-rainbow/perform-e2e-test"><img src="https://agentmods.dev/badge/commands/dauquangthanh/hanoi-rainbow/perform-e2e-test/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/commands/dauquangthanh/hanoi-rainbow/perform-e2e-test"><img src="https://agentmods.dev/badge/commands/dauquangthanh/hanoi-rainbow/perform-e2e-test.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.00020 | $0.04077 |
| Opus 5 | $0.00010 | $0.02039 |
| Sonnet 5 | $0.00004 | $0.00815 |
| Haiku 4.5 | $0.00002 | $0.00408 |
Grade A, and why
perform-e2e-test 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- rainbow.perform-e2e-test — 97% identical, 21 lines differ
How it starts
The opening of the file, as written. The whole thing — 511 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
IMPORTANT: Automatically generate a 'test:' prefixed git commit message (e.g., 'test: add E2E test results and execution report') and commit test scripts, results, and reports upon completion.
-
Setup: Run
{SCRIPT}from repo root and parse JSON for E2E_TEST_PLAN, TEST_RESULTS_DIR, TIMESTAMP. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot"). -
Load context: Read
docs/e2e-test-plan.md,docs/architecture.md,docs/standards.md(if exists), andmemory/ground-rules.md. Parse test scenarios, priorities, and execution requirements. Adhere to the principles for maximizing system clarity, structural simplicity, and long-term maintainability. -
Execute E2E test workflow: Follow the execution plan from E2E_TEST_PLAN to:
- Generate test scripts from test scenarios
- Set up test environment and test data
- Execute test suites (smoke, regression, or full)
- Capture test results, screenshots, and logs
- Generate detailed test result report
- Analyze failures and identify root causes
-
Stop and report: Command ends after test execution and report generation. Report test results file path, pass/fail summary, and critical failures.
Phases
Phase 0: Test Preparation & Environment Setup
-
Parse E2E test plan:
- Read
docs/e2e-test-plan.md - Extract test scenarios by priority (P0, P1, P2, P3)
- Identify test data requirements
- Review test environment configuration
- Parse test framework and tool specifications
- Read
-
Determine test suite to execute:
- Smoke: P0 critical scenarios only (~10-15 min)
- Regression: P0 + P1 scenarios (~1 hour)
- Full: All scenarios P0-P3 (~3-4 hours)
- Custom: User-specified scenario selection
- Default to Smoke if not specified
-
Validate prerequisites:
- Check test environment availability
- Verify test framework installation
- Validate test data is accessible
- Ensure database/services are running
- Confirm external service mocks are configured
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.
- 8d ago First seen · 511 lines · 20 tokens per session scan A 2d1cf3dc1124
perform-e2e-test is a command published in the GitHub repository DauQuangThanh/hanoi-rainbow (16 stars, last pushed 7mo ago), licensed MIT. It adds 20 tokens to every session and 4,077 once invoked, about $0.0001 per session on Opus 5. 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
distill
Creates E2E acceptance tests in Given-When-Then format from requirements and architecture. Use when preparing executable specifications before implementation.
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…
gba-test
$ARGUMENTS: test mode — game profile defines available modes (e.g., smoke, gameplay, save, stress, full, ai, battle, nav, custom ).
final-review
Command "final-review" from adriannoes/awesome-agentic-ai, covering final review - comprehensive pr review & testing, step 0: determine review pass, step 1: create or update the pr, step 2: launch three review agents in parallel and agent 1: codebase consistency reviewer.
auto-canary
A command for deployment verification that runs a build, end-to-end tests, and browser health checks. End-to-end tests check a complete user flow across the application rather than only one small part.