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 thiientv/godmode --skill browser-testinggit clone --depth 1 https://github.com/thiientv/godmodeWrote 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/thiientv/godmode/browser-testing)<a href="https://agentmods.dev/skills/thiientv/godmode/browser-testing"><img src="https://agentmods.dev/badge/skills/thiientv/godmode/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/thiientv/godmode/browser-testing"><img src="https://agentmods.dev/badge/skills/thiientv/godmode/browser-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.00378 |
| Opus 5.5 | $0.00027 | $0.00151 |
| Sonnet 5.5 | $0.00014 | $0.00076 |
| Haiku 4.5 | $0.00007 | $0.00038 |
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 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.
What it actually says
Browser Testing
Exercise the user boundary with deterministic data and meaningful assertions.
Build the test
- Identify the route, user role, starting state, and supported viewport.
- Wait on semantic readiness—role, label, URL, response, or visible state—not arbitrary sleeps.
- Assert the user outcome, important error path, and relevant network/API behavior. Prefer accessible locators over CSS implementation details.
- Cover keyboard flow and at least the narrowest supported viewport for responsive work.
- Freeze clocks, animations, random IDs, remote data, and fonts only when the test requires stable visual evidence; do not hide real regressions.
- Capture screenshots at stable component/page boundaries and review diffs before updating baselines.
Use browser-checklist.md for Playwright,
DevTools, and non-Playwright equivalents. Use frontend-design for design
decisions and ui-ux-review for an independent visual pass.
Safety and flake control
Use test accounts and fixtures. Do not send destructive actions to production. Record browser, viewport, locale, timezone, and feature flags. Investigate flakes instead of increasing timeouts until they disappear.
Completion condition
The browser test proves the requested user behavior at the real boundary, is repeatable, covers the relevant state/viewport, and reports visual or environment limits.
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.
- 1mo ago First seen · 44 lines · 68 tokens per session scan A da8dfcaf3962
browser-testing is a skill published in the GitHub repository thiientv/godmode (99 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 378 once invoked, about $0.0003 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-30.
Other skills, from other repositories
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
browser-qa
A live browser quality-checking workflow that replays user journeys with Playwright-compatible scripts, screenshots, and reports. It stores test cases and run evidence under `.agents/qa/`.
browser-automation
Playwright browser automation via MCP. Covers E2E testing, UI review, web scraping, screenshot capture, and general browser interaction. MCP-first — CLI is fallback only.
playwright
Playwright end-to-end testing best practices for web applications, covering test design, locator strategies, and assertion patterns.
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.