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 FaisalNoman/playwright-skills --skill e2e-dashboardgit clone --depth 1 https://github.com/FaisalNoman/playwright-skillsWrote 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/faisalnoman/playwright-skills/e2e-dashboard)<a href="https://agentmods.dev/skills/faisalnoman/playwright-skills/e2e-dashboard"><img src="https://agentmods.dev/badge/skills/faisalnoman/playwright-skills/e2e-dashboard/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/faisalnoman/playwright-skills/e2e-dashboard"><img src="https://agentmods.dev/badge/skills/faisalnoman/playwright-skills/e2e-dashboard.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.00030 | $0.03807 |
| Opus 5.5 | $0.00012 | $0.01523 |
| Sonnet 5.5 | $0.00006 | $0.00761 |
| Haiku 4.5 | $0.00003 | $0.00381 |
Grade A, and why
e2e-dashboard 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Dashboard Installer
What Gets Installed
Three files wired into Playwright:
| File | Purpose |
|---|---|
{reporters_dir}/progress-server.js |
Node HTTP server (port 7373) — receives events, serves SSE, spawns test runs |
{reporters_dir}/realtime-reporter.js |
Playwright custom reporter — POSTs events to server as tests run |
{tests_dir}/test-progress-dashboard.html |
Single-page dashboard served at http://localhost:7373 |
25 features: live SSE stream · sidebar file filter · category tabs (auto-hidden when only one test category — E2E, Security, or Perf — is installed) · per-file/per-test run buttons · re-run failed · failures-only toggle · test name search · sort (default/failed-first/slowest) · describe-block nesting · flakiness badge (from run history) · ETA during run · screenshot thumbnails · Playwright Trace Viewer integration · copy error button · browser notifications · compact mode · keyboard shortcuts · auto-scroll to first failure · failure grouping by error pattern · video attachments · Markdown failure export · static CI-report mode · per-test run-history strip · inline spec source view + edit-and-save (writes back to disk via the same file whitelist /run uses) · browser selector (multi-select, auto-hidden when only one browser is configured) with grouped per-test results and a per-browser pass/fail summary strip.
Security model: the server binds to 127.0.0.1 only (never reachable off the local machine), locks CORS to its own origin (no wildcard), and requires an X-Dashboard-Token header — generated at startup and printed to the console — on every state-changing route (/run, /stop, /open-trace, /filetests). The served dashboard HTML has the token injected automatically; nothing to configure. Set E2E_DASHBOARD_TOKEN to pin a fixed token (e.g. for scripted use), and E2E_DASHBOARD_PORT to pin a starting port (auto-falls-back by +1 up to 10 times if it's taken, so multiple projects' dashboards can run concurrently).
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.
- 1mo ago First seen · 250 lines · 30 tokens per session scan A 7a566e2b24f9
e2e-dashboard is a skill published in the GitHub repository FaisalNoman/playwright-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 3,807 once invoked, about $0.0001 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
e2e
Add durable end-to-end tests for user/API-visible behavior. Detect or scaffold the E2E framework, write tests, run the app, and store evidence. Use for E2E, Playwright/Cypress, regression tests, or quality gates. Not exploratory QA.
mirrord-ci
Help users set up mirrord in CI pipelines for testing against real Kubernetes environments. Use when users want to run end-to-end tests, integration tests, or automated tests in CI using mirrord to connect to staging/shared clusters.
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…
test-site
Tests a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification via Playwright. Use when the user wants to test, verify, or smoke-test their deployed site.
running-livekit-simulations
Runs LiveKit agent simulations and acts on the results. Use when the user says "run my simulations", "regression test my agent before deploying", "run the scenarios", "use lk agent simulate", "did my agent pass", "why did this scenario fail", "run simulations in CI", "test the audio pipeline", "check turn-taking and…