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 erikfiala/e2e-tester --skill testergit clone --depth 1 https://github.com/erikfiala/e2e-testerWrote 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/erikfiala/e2e-tester/tester)<a href="https://agentmods.dev/skills/erikfiala/e2e-tester/tester"><img src="https://agentmods.dev/badge/skills/erikfiala/e2e-tester/tester/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/erikfiala/e2e-tester/tester"><img src="https://agentmods.dev/badge/skills/erikfiala/e2e-tester/tester.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.00067 | $0.00590 |
| Opus 5 | $0.00034 | $0.00295 |
| Sonnet 5 | $0.00013 | $0.00118 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
tester 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Playwright + Lighthouse Tester
Use this skill to run reproducible e2e and Lighthouse checks across a target web repo, with discovery-first command selection and clear reporting.
Workflow
-
Discover first
- Run:
python3 .cursor/skills/tester/scripts/discover_audit_targets.py .- Optional JSON output:
python3 .cursor/skills/tester/scripts/discover_audit_targets.py . --json
- Read discovered package scripts, runner files, and PWA signals before deciding what to run.
- Run:
-
Runner selection priority
- Prefer existing
npm/pnpm/yarnscripts that already run Playwright and Lighthouse. - Otherwise use checked-in runner files in common locations (
perf/,scripts/,e2e/,tests/). - Only use ad-hoc
npx playwright/npx lighthousecommands if no native runner exists.
- Prefer existing
-
Execution matrix
- For Lighthouse, target all slices when technically possible:
light-desktoplight-mobiledark-desktopdark-mobile
- Attempt categories:
performanceaccessibilitybest-practicesseopwa(when supported by installed Lighthouse and app signals)
- Prefer preview or production-like mode instead of noisy local dev mode when the repo supports it.
- For Lighthouse, target all slices when technically possible:
-
100/100 objective
- Always optimize toward 100/100 in Lighthouse categories and Web Vitals-related audits.
- Do not claim false success; explicitly list blockers and remaining deltas to 100.
Reporting contract
Always report by package/surface:
- Commands run, including whether native or adapted.
- Playwright findings: failing flows, flaky clues, console/page errors, failed requests, auth blockers.
- Lighthouse findings per matrix slice (
light-desktop,light-mobile,dark-desktop,dark-mobile). - A dedicated 100/100 gap analysis section with highest impact opportunities.
- Explicit coverage gaps (skipped routes, no dark mode, no mobile emulation, missing credentials, unsupported PWA category).
What ships with it
1 file 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.
- 8d ago First seen · 56 lines · 67 tokens per session scan A e3e2d7a22403
tester is a skill published in the GitHub repository erikfiala/e2e-tester (2 stars, last pushed 5mo ago), licensed MIT. It adds 67 tokens to every session and 590 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-31.
Other skills, from other repositories
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…
frontend-visual-qa
Verify rendered frontend evidence after implementation, including screenshot comparison, responsiveness, overflow, visible states, and scoped visual regression. Use available browser tooling only; exclude static lookup, routine code review, lint, builds, onboarding, and tool detection.
playwright-skill
Battle-tested Playwright patterns for writing, debugging, and scaling reliable test suites. Use when you need guidance for E2E, API, component, visual, accessibility, or security testing, plus CI/CD, CLI automation, page objects, and migration from Cypress or Selenium. TypeScript and JavaScript.
playwright-core
Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests. Use when you need locator strategy, assertions, fixtures, network mocking, auth flows, trace debugging, or framework recipes for React, Next.js, Vue, and Angular. TypeScript and…
harness-design
Quality harness for design-dna Phase 3 output with browser-based visual verification. After an agent generates a design from a Design DNA JSON + user content, this skill acts as a verification and scoring layer — collecting all page resources via console/network inspection, performing section-by-section screenshot…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.