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 sei-newbear/xp-harness --skill e2e-playwright-frontgit clone --depth 1 https://github.com/sei-newbear/xp-harnessWrote 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/sei-newbear/xp-harness/e2e-playwright-front)<a href="https://agentmods.dev/skills/sei-newbear/xp-harness/e2e-playwright-front"><img src="https://agentmods.dev/badge/skills/sei-newbear/xp-harness/e2e-playwright-front/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/skills/sei-newbear/xp-harness/e2e-playwright-front"><img src="https://agentmods.dev/badge/skills/sei-newbear/xp-harness/e2e-playwright-front.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.00088 | $0.00691 |
| Opus 5.5 | $0.00035 | $0.00276 |
| Sonnet 5.5 | $0.00018 | $0.00138 |
| Haiku 4.5 | $0.00009 | $0.00069 |
Grade A, and why
e2e-playwright-front 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 2mo 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.
What it actually says
front E2E の流儀 (Playwright)
このプロジェクトの E2E は「動作確認スクリプト」ではなく仕様書として読めることを目指す。迷ったら「非エンジニアが読んで意図を追えるか」で判断する。
セレクタはユーザー視点で
優先順位: getByRole (役割と文言) → getByLabel / getByText (見える文字) → getByTestId → page.locator('#id') は最終手段。ID セレクタは実装詳細に結合し、仕様書としての価値を失う。
操作はヘルパー関数 (日本語名) に切り出す
- テスト本体はステップを並べただけに見える状態を保つ。Playwright API の生呼び出しは
e2e/steps/のヘルパーに隠蔽する - 関数名は日本語で意図を表現する (例:
メモを追加する(page, { 本文 })) - テスト本体に
page.click/page.locator/expect(page...)が出てきたらヘルパーへ昇格させるサイン - ヘルパーは嘘をつかない: 受け取った引数は実装内で必ず使う
前提 (GIVEN) と行動 (WHEN/THEN) を describe / test で分離する
- GIVEN:
test.describeの名前 (名詞句) +beforeEachで前提状態を作る - WHEN/THEN:
test本体 (動詞句で始まり結果まで言い切る名前) - 外側 describe (機能名) > 内側 describe (GIVEN 句) > test 名 を連結すると、完結した日本語の仕様文になるのが目印
テスト独立性
- 前提となる状態は必ず
beforeEachで自分で作る (他テストの副作用に頼らない、afterEachだけに頼らない) - 実行順序が変わっても、単独で実行しても、正しく動くこと
ファイル配置
- spec は
e2e/specs/<シナリオ名>.spec.ts、1 ファイル 1 シナリオ。連番は付けない - ヘルパーは
e2e/steps/配下
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.
- 2mo ago First seen · 35 lines · 88 tokens per session scan A cc3c9a657b3e
e2e-playwright-front is a skill published in the GitHub repository sei-newbear/xp-harness (9 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 691 once invoked, about $0.0004 per session on Opus 5.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 skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.