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 OKHP3/skillz --skill browser-testinggit clone --depth 1 https://github.com/OKHP3/skillzWrote 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/okhp3/skillz/browser-testing)<a href="https://agentmods.dev/skills/okhp3/skillz/browser-testing"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/browser-testing/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/okhp3/skillz/browser-testing"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/browser-testing.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.00096 | $0.01240 |
| Opus 5 | $0.00048 | $0.00620 |
| Sonnet 5 | $0.00019 | $0.00248 |
| Haiku 4.5 | $0.00010 | $0.00124 |
Grade A, and why
browser-testing 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 6d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser testing
Browser tests are the most expensive tests you own — slowest to run, most likely to break for reasons unrelated to your code, hardest to debug. That cost buys one thing nothing else does: proof that the pieces work together in a real browser.
Spend that budget on a small number of journeys that must never break. A large E2E suite is not thorough; it is slow, flaky, and eventually ignored, and an ignored suite provides no safety while still consuming CI time.
Rule of thumb: if a case can be covered below the UI, cover it there. E2E is for the wiring.
1. Choose the journeys
Pick the paths where failure is unacceptable, typically five to fifteen for a whole product:
- Sign up, sign in, sign out
- The core action the product exists for
- Anything involving money
- The path most users take on first visit
For each, test the happy path plus the one failure that matters (declined card, taken username). Every remaining permutation belongs in a cheaper test.
Done when: the journey list is written and short enough to defend.
2. Select elements the way a user identifies them
Selector choice determines whether the suite survives a redesign. In order of preference:
- Role and accessible name —
getByRole("button", { name: "Save" }). Closest to how a person finds the control, and it fails when accessibility breaks, which is a real bug. - Visible text —
getByText, for non-interactive content. - Dedicated test attributes —
data-testid. Explicit contract, immune to restyling. Use when the first two are ambiguous. - CSS or XPath structure, a last resort.
div > div:nth-child(3) > spanencodes the DOM shape, and it breaks on a layout change that broke nothing for users.
Done when: no selector in the suite depends on the DOM's structure.
3. Never wait for time
Fixed sleeps are the single largest source of flakiness. sleep(2000) is simultaneously too
long on a fast machine and too short on a loaded CI runner — it wastes time and fails
randomly, the worst of both.
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.
- 6d ago First seen · 113 lines · 96 tokens per session scan A 87341149bcc9
browser-testing is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 1,240 once invoked, about $0.0005 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-09-03.
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.
webapp-testing
Browser-tests a local webapp end to end — starts the app, installs Playwright if missing, writes a spec for the critical path plus edge cases, runs headless, captures screenshots, console and network logs on failure, and reports a pass/fail table with repro steps. Degrades to curl smoke tests when no browser is…
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.