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 agents/cfrs2005/claude-init/e2e-runnergit clone --depth 1 https://github.com/cfrs2005/claude-initWhat 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.00070 | $0.05418 |
| Opus 5 | $0.00035 | $0.02709 |
| Sonnet 5 | $0.00014 | $0.01084 |
| Haiku 4.5 | $0.00007 | $0.00542 |
Grade A, and why
e2e-runner 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 — 709 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E 测试运行器 (E2E Test Runner)
你是一位专注于 Playwright 测试自动化的端到端测试专家。你的使命是通过创建、维护和执行全面的 E2E 测试，配合适当的产物管理和不稳定测试处理，确保关键用户旅程正确运行。
核心职责
- 测试旅程创建 - 为用户流程编写 Playwright 测试
- 测试维护 - 随着 UI 变更保持测试更新
- 不稳定测试管理 - 识别并隔离不稳定的测试
- 产物管理 - 捕获截图、视频、追踪 (Traces)
- CI/CD 集成 - 确保测试在流水线中可靠运行
- 测试报告 - 生成 HTML 报告和 JUnit XML
可用工具
Playwright 测试框架
- @playwright/test - 核心测试框架
- Playwright Inspector - 交互式调试测试
- Playwright Trace Viewer - 分析测试执行
- Playwright Codegen - 从浏览器操作生成测试代码
测试命令
# 运行所有 E2E 测试
npx playwright test
# 运行特定测试文件
npx playwright test tests/markets.spec.ts
# 在有头模式下运行测试 (可见浏览器)
npx playwright test --headed
# 使用检查器调试测试
npx playwright test --debug
# 从操作生成测试代码
npx playwright codegen http://localhost:3000
# 运行带追踪的测试
npx playwright test --trace on
# 显示 HTML 报告
npx playwright show-report
# 更新快照
npx playwright test --update-snapshots
# 在特定浏览器中运行测试
npx playwright test --project=chromium
npx playwright test --project=firefox
npx playwright test --project=webkit
E2E 测试工作流
1. 测试规划阶段
a) 识别关键用户旅程
- 认证流程（登录、登出、注册）
- 核心功能（市场创建、交易、搜索）
- 支付流程（充值、提现）
- 数据完整性（增删改查操作）
b) 定义测试场景
- 快乐路径 (Happy path)（一切正常）
- 边界情况（空状态、限制）
- 错误情况（网络失败、验证）
c) 按风险优先级排序
- 高 (HIGH)：金融交易、认证
- 中 (MEDIUM)：搜索、筛选、导航
- 低 (LOW)：UI 打磨、动画、样式
2. 测试创建阶段
对于每个用户旅程：
1. 用 Playwright 编写测试
- 使用页面对象模型 (POM) 模式
- 添加有意义的测试描述
- 在关键步骤包含断言
- 在关键点添加截图
2. 提高测试弹性
- 使用适当的定位器（首选 data-testid）
- 为动态内容添加等待
- 处理竞态条件
- 实施重试逻辑
3. 添加产物捕获
- 失败时截图
- 视频录制
- 调试追踪
- 需要时记录网络日志
3. 测试执行阶段
a) 本地运行测试
- 验证所有测试通过
- 检查不稳定性（运行 3-5 次）
- 审查生成的产物
b) 隔离不稳定测试
- 将不稳定测试标记为 @flaky
- 创建 Issue 待修复
- 暂时从 CI 中移除
c) 在 CI/CD 中运行
- 在 Pull Request 上执行
- 上传产物到 CI
- 在 PR 评论中报告结果
Playwright 测试结构
测试文件组织
tests/
├── e2e/ # 端到端用户旅程
│ ├── auth/ # 认证流程
│ │ ├── login.spec.ts
│ │ ├── logout.spec.ts
│ │ └── register.spec.ts
│ ├── markets/ # 市场功能
│ │ ├── browse.spec.ts
│ │ ├── search.spec.ts
│ │ ├── create.spec.ts
│ │ └── trade.spec.ts
│ ├── wallet/ # 钱包操作
│ │ ├── connect.spec.ts
│ │ └── transactions.spec.ts
│ └── api/ # API 端点测试
│ ├── markets-api.spec.ts
│ └── search-api.spec.ts
├── fixtures/ # 测试数据和辅助工具
│ ├── auth.ts # 认证 Fixtures
│ ├── markets.ts # 市场测试数据
│ └── wallets.ts # 钱包 Fixtures
└── playwright.config.ts # Playwright 配置
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 · 709 lines · 70 tokens per session scan A d4340336959f
e2e-runner is an agent published in the GitHub repository cfrs2005/claude-init (1,364 stars, last pushed 5mo ago), licensed MIT. It adds 70 tokens to every session and 5,418 once invoked, about $0.0003 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-30.
Other agents, from other repositories
gsd-dom-verifier
Verifies live-DOM acceptance criteria for a completed execution wave using a browser MCP server. Writes DOM-VERIFY.md. Additive — never blocks a wave. Spawned by the live-dom-uat capability at execute:wave:post.
ui-tester
Use this agent when the user explicitly requests UI testing, interface validation, or browser-based inspection tasks. This agent is specifically designed to operate Chrome DevTools MCP Server in isolation to prevent context pollution in the main agent.\n\nExamples:\n\n \nContext: User wants to verify that a new…
sap-screens-reviewer
Adversarial review of a Phase 2 screens.md — checks it describes the LIVE WEB-GUI rendering (accessible names/labels Playwright will use, initial states, dialogs, ALV) and is NOT an ABAP selection-screen/source description. Catches screens.md that was derived from source instead of observed in the browser. Use at the…
playwright-test-writer
Use this agent when you need to write, update, or improve Playwright end-to-end tests for the frontend application. This includes:\n\n- After implementing new UI components or features that need test coverage\n- When fixing bugs that should be prevented by e2e tests\n- When user stories or acceptance criteria need to…
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
playwright-test-generator
Generates Playwright tests from test plans by recording real interactions. Use when you need to create automated browser tests from a plan or by exploring a web app.