What is rainbow.design-e2e-test?

A command that designs end-to-end test specifications for an entire product. These specifications describe complete user journeys and how they should be tested.

Use it to define critical user journeys, integration scenarios, test data handling, automation requirements, and a test plan.

It organizes test coverage before tests are run, including data, environments, tools, and execution plans.

How DauQuangThanh/sso-mcp-server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to DauQuangThanh/sso-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/DauQuangThanh/sso-mcp-server/main/.claude/commands/rainbow.design-e2e-test.md

Clone the repo

git clone --depth 1 https://github.com/DauQuangThanh/sso-mcp-server

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/dauquangthanh/sso-mcp-server/rainbow.design-e2e-test/github.svg)](https://agentmods.dev/commands/dauquangthanh/sso-mcp-server/rainbow.design-e2e-test)

Your own site

<a href="https://agentmods.dev/commands/dauquangthanh/sso-mcp-server/rainbow.design-e2e-test"><img src="https://agentmods.dev/badge/commands/dauquangthanh/sso-mcp-server/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/dauquangthanh/sso-mcp-server/rainbow.design-e2e-test"><img src="https://agentmods.dev/badge/commands/dauquangthanh/sso-mcp-server/rainbow.design-e2e-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,782 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 92% copy Near-identical to another mod in the catalogue.

Token cost

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.02782
Opus 5	$0.00010	$0.01391
Sonnet 5	$0.00004	$0.00556
Haiku 4.5	$0.00002	$0.00278

Measured 8d ago against content hash 7d3f3bbe836c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

rainbow.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 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.

Origin

This is a copy

92% identical to design-e2e-test — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/rainbow.design-e2e-test.md · 308 lines

How it starts

The opening of the file, as written. The whole thing — 308 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 .rainbow/scripts/bash/setup-design-e2e-test.sh --json 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 from specs/*/spec.md. Load E2E_TEST_DOC template (already copied to docs/).
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.md files
- 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)

Read the full file on GitHub · 308 lines

Changes

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 · 308 lines · 21 tokens per session scan A 7d3f3bbe836c

Subscribe to this mod's changes

rainbow.design-e2e-test is a command published in the GitHub repository DauQuangThanh/sso-mcp-server (0 stars, last pushed 8mo ago), licensed MIT. It adds 21 tokens to every session and 2,782 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to design-e2e-test, differing in 27 lines, and is treated as a copy.

E2E testing Testing

sso-mcp-server: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

User Input

Outline

Phases

Phase 0: Test Strategy & Scope Definition

What this file has done since we first saw it

Other commands, from other repositories

playwright-test-heal

paul:verify

webapp-testing

ui-snapshot.template

laravel-playwright

qa