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/DauQuangThanh/hanoi-rainbowWrote 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/design-e2e-test)<a href="https://agentmods.dev/commands/dauquangthanh/hanoi-rainbow/design-e2e-test"><img src="https://agentmods.dev/badge/commands/dauquangthanh/hanoi-rainbow/design-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/design-e2e-test"><img src="https://agentmods.dev/badge/commands/dauquangthanh/hanoi-rainbow/design-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.00021 | $0.02857 |
| Opus 5 | $0.00010 | $0.01429 |
| Sonnet 5 | $0.00004 | $0.00571 |
| Haiku 4.5 | $0.00002 | $0.00286 |
Grade A, and why
design-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 9d 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.design-e2e-test — 92% identical, 27 lines differ
How it starts
The opening of the file, as written. The whole thing — 313 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 plan and specifications') and commit upon completion.
-
Setup: Run
{SCRIPT}from repo root and parse JSON for E2E_TEST_DOC, DOCS_DIR, ARCH_DOC, SPECS_DIR. 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
memory/ground-rules.md,docs/architecture.md,docs/standards.md(if exists), and all feature specifications fromspecs/*/spec.md. Load E2E_TEST_DOC template (already copied to docs/). Adhere to the principles for maximizing test case clarity, simplicity, and long-term execution maintainability. -
Execute E2E test design workflow: Follow the structure in E2E_TEST_DOC template to:
- Define E2E test strategy and scope
- Identify critical user journeys from feature specs
- Design test scenarios covering system integration points
- Define test data management strategy
- Rainbow test environment requirements
- Document test automation framework and tools
- Create test execution plan
-
Stop and report: Command ends after E2E test document completion. Report E2E_TEST_DOC path and generated artifacts.
Phases
Phase 0: Test Strategy & Scope Definition
-
Analyze architecture and features:
- Read architecture.md to understand system components
- Read all
specs/*/spec.mdfiles - Identify integration points between components
- Map external system dependencies
- Review ground-rules for testing constraints
-
Define E2E test scope:
- Identify what is IN scope (critical paths, integrations)
- Identify what is OUT of scope (unit-level, component-level)
- Define testing boundaries (UI-to-database, API-to-API, etc.)
- Determine test coverage goals
-
Select test approach:
- UI-driven E2E tests (Selenium, Cypress, Playwright)
- API-driven E2E tests (REST Assured, Postman, Supertest)
- Mobile E2E tests (Appium, Detox)
- Mixed approach (UI + API + Database validation)
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.
- 9d ago First seen · 313 lines · 21 tokens per session scan A 12a51c979f5b
design-e2e-test is a command published in the GitHub repository DauQuangThanh/hanoi-rainbow (16 stars, last pushed 7mo ago), licensed MIT. It adds 21 tokens to every session and 2,857 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.