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 skills add medalsoftchina/workcopilot --skill doa-testreportgit clone --depth 1 https://github.com/medalsoftchina/workcopilotWrote 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/skills/medalsoftchina/workcopilot/doa-testreport)<a href="https://agentmods.dev/skills/medalsoftchina/workcopilot/doa-testreport"><img src="https://agentmods.dev/badge/skills/medalsoftchina/workcopilot/doa-testreport.svg" alt="Measured on agentmods" 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.00127 | $0.01790 |
| Opus 5 | $0.00063 | $0.00895 |
| Sonnet 5 | $0.00025 | $0.00358 |
| Haiku 4.5 | $0.00013 | $0.00179 |
Grade A, and why
doa-e2etest 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 7d 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.
This is a copy
100% identical to doa-e2etest — 0 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test → Report Pipeline
Playwright 端到端测试全流程 skill：从环境搭建到生成精美的 HTML/PDF 测试报告。
When to Use
- 需要为前端项目搭建 E2E 测试
- 需要编写或补充 Playwright 测试用例
- 需要运行测试并生成可交付的报告（HTML / PDF）
- 项目验收、迭代交付时需要测试报告产物
Procedure
Phase 1: 环境检测与安装
-
检测前端技术栈
- 读取
package.json确认框架（React/Vue/Next.js/Angular 等） - 确认 UI 组件库（Ant Design / Element Plus / MUI 等）
- 确认构建工具（Vite / Webpack / Next.js 内置等）
- 确认前端开发服务器端口
- 读取
-
安装 Playwright
npm install -D @playwright/test -
检测可用浏览器
- 优先尝试
npx playwright install chromium - 如网络受限，使用系统已安装的浏览器：
- Windows:
channel: 'msedge' - macOS:
channel: 'chrome'
- Windows:
- 在配置中设置正确的 channel
- 优先尝试
-
生成 playwright.config.ts
- 参考 配置模板
- 根据实际检测结果填充
baseURL、channel、testDir等
-
添加 npm scripts
{ "test:e2e": "playwright test", "test:e2e:ui": "playwright test --ui" }
Phase 2: 编写测试用例
-
分析应用路由和页面
- 读取路由配置文件（
routes/index.tsx等） - 识别所有可测试页面
- 读取路由配置文件（
-
按功能模块组织测试文件
- 目录结构：
e2e/{module}.spec.ts - 每个文件对应一个功能模块
- 目录结构：
-
测试用例编写规则
- 参考 测试编写指南
- 使用中文测试标题（
test('应显示登录表单', ...)） - 优先使用语义化定位器（
getByRole、getByText、getByPlaceholder） - 为需要登录的测试创建
login辅助函数 - 每个
describe块使用beforeEach处理前置条件
-
常见陷阱处理
- Ant Design 按钮文本可能有空格（如 "登 录"），使用正则：
/登\s*录/ networkidle等待确保页面资源完全加载- 401 拦截器可能干扰登录测试，检查 axios 拦截器逻辑
- Strict mode 报错时缩小选择器范围（如
.ant-result-title）
- Ant Design 按钮文本可能有空格（如 "登 录"），使用正则：
Phase 3: 执行测试
-
确认服务可用
- 检查前端 dev server 是否运行
- 检查后端 API 是否运行
- 如未运行，提示用户启动或使用
webServer配置自动启动
-
运行测试
npx playwright test --reporter=list -
失败用例调试
- 分析错误信息，定位原因
- 常见原因：选择器不匹配、超时、网络请求失败
- 修复后重新运行验证
-
导出 JSON 结果
npx playwright test --reporter=json 2>$null | Out-File -Encoding utf8 playwright-report/results.json
Phase 4: 生成测试报告
- 读取 JSON 测试结果
- 解析
playwright-report/results.json - 提取：套件信息、用例状态、耗时、时间线
- 解析
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 165 lines · 127 tokens per session scan A d064415f7d09
doa-e2etest is a skill published in the GitHub repository medalsoftchina/workcopilot (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 127 tokens to every session and 1,790 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to doa-e2etest, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
devlab-web-visual-ops
A browser-based operations guide for web applications, including single-page apps, micro-frontends, and multi-page sites. It covers observing, navigating, interacting, inspecting, validating, and capturing pages with browser automation and visual fallbacks.
e2e-playwright
Use when writing end-to-end browser tests with Playwright. Covers resilient locators, auto-waiting, network interception, authentication reuse, parallelization, and eliminating flakiness.
web-app-testing
Use when testing a web application interactively — verifying a feature, reproducing a bug, or checking a flow in a real browser. Covers systematic exploration, console and network inspection, and reporting what you find.