Borrowing it
Nothing to install: this file belongs to theimaginaryfoundation/what-iff. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/theimaginaryfoundation/what-iff/main/.agents/skills/playwright-e2e/SKILL.mdgit clone --depth 1 https://github.com/theimaginaryfoundation/what-iffWrote 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/theimaginaryfoundation/what-iff/playwright-e2e)<a href="https://agentmods.dev/skills/theimaginaryfoundation/what-iff/playwright-e2e"><img src="https://agentmods.dev/badge/skills/theimaginaryfoundation/what-iff/playwright-e2e/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/theimaginaryfoundation/what-iff/playwright-e2e"><img src="https://agentmods.dev/badge/skills/theimaginaryfoundation/what-iff/playwright-e2e.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.00148 | $0.01657 |
| Opus 5.5 | $0.00059 | $0.00663 |
| Sonnet 5.5 | $0.00030 | $0.00331 |
| Haiku 4.5 | $0.00015 | $0.00166 |
Grade A, and why
playwright-e2e 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 1mo 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright E2E
Browser-level tests against the real Angular app, in
web/app/e2e. This skill is a decision-tree pointer — for
full detail read web/app/e2e/README.md (layout, configs,
visual-regression internals, and the reasoning behind the structure) rather
than expecting it duplicated here.
All commands below run from web/app/ and always go through
the repo's @playwright/test devDependency via npx playwright / the npm
scripts — never install or invoke a separately pinned/global Playwright.
Which config?
| Need | Command | Notes |
|---|---|---|
| Everyday local run (default) | npm run e2e or npm run e2e:mock-llm |
backend on LLM_BACKEND=mock, Playwright starts the Angular dev server |
| Exercise a real (small) local model | npm run e2e:local-llm |
excludes @visual, @mock-only |
| Against your own deployment | supply your own config — see the README's "Running against your own deployment" | spread baseConfig, set use.baseURL, omit localWebServer; never record video, keep traces retain-on-failure |
| Interactive debugging | npm run e2e -- --ui |
|
| Just the visual specs (diagnostic only, not baseline-accurate) | npm run e2e:mock-llm:visual |
host run, will NOT match committed Linux baselines |
mock is the default and what you should reach for unless the task
specifically needs another environment. There is no root
playwright.config.ts — every invocation needs --config (the npm scripts
already pass it).
Backend prerequisites
The local configs' webServer only starts the Angular dev server, never the
backend. Before running e2e/e2e:mock-llm/e2e:local-llm:
make db-up
make dev-up # or: make run-mock / make run-local
dev/prod configs require E2E_BASE_URL and E2E_API_BASE_URL and throw
immediately if either is missing.
Writing tests: POM conventions
e2e/poms/holds Page Object Models: locators and interactions only — no assertions, no env-awareness. Assertions live in the spec.- Grow an existing POM rather than reaching into a spec with a raw locator.
If the page doesn't have a POM yet, add one following the existing files
in
e2e/poms/(index.tsre-exports them all). - Locate by
aria-label, role, or placeholder — the app has nodata-testidattributes, and adding them isn't the established pattern here. - Specs live under
e2e/tests/{functional,journeys,visual,a11y}/, grouped by feature (seefunctional/auth/,functional/personality/,functional/profile/).
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.
- 1mo ago Changed · +26 lines b3ba9bf31dde
- 1mo ago First seen · 129 lines · 148 tokens per session scan A eb20f5ffe784
playwright-e2e is a skill published in the GitHub repository theimaginaryfoundation/what-iff (19 stars, last pushed today), licensed Apache-2.0. It adds 148 tokens to every session and 1,657 once invoked, about $0.0006 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-09-09.
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.
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.