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 OutlineDriven/outline-driven-development --skill browser-testinggit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/browser-testing)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/browser-testing"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/browser-testing.svg" alt="Measured on agentmods" 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.00044 | $0.02882 |
| Opus 5 | $0.00022 | $0.01441 |
| Sonnet 5 | $0.00009 | $0.00576 |
| Haiku 4.5 | $0.00004 | $0.00288 |
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 yesterday.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser testing
Contract
| Field | Bound contract |
|---|---|
| Trigger | Browser UI implementation, debugging, or runtime verification; or a PR number, branch name, or current to test pages affected by a diff. |
| Authority | Reversible local: writes only evidence artifacts (screenshots, console logs, test reports); rollback is deletion. Source, VCS, credential, paid, published, deployed, and remote mutation stay prohibited. Fixes are requested from the user, never applied. |
| Side effect | Drives an attached browser or a selected browser driver against the local dev server. Writes only local evidence artifacts (screenshots, console logs, test reports). |
| Done | Interactive: the changed runtime surface is exercised with clean console/network and correct visual, accessibility, or performance evidence. Diff-scoped: the summary reports every affected route as Pass, Fail, or Skip with reasons, or reports the preflight blocker and what would clear it. |
Inputs
Interactive mode
- A browser-rendered change to verify or debug (required): the localhost or dev-server URL of the affected page and a description of the surface that changed.
- Chrome DevTools MCP attached (required): an MCP server providing screenshot, DOM inspection, console logs, network monitor, performance trace, element computed-styles, accessibility tree, and page-context JavaScript execution tools.
- The symptom or verification target (required for debugging, optional for verification): what is wrong, or what must be confirmed.
- Logged-in browser state (optional): only when the test genuinely needs authenticated state; defaults to an isolated profile.
Diff-scoped mode
- A target (required): a PR number, a branch name, the literal
current, or omitted (treated ascurrent). Optional--port PORToverrides dev-server port detection. - A git repository with changes to test (required).
- A running local dev server (required before any route is exercised; the run stops at preflight if none is reachable).
What ships with it
4 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.
- yesterday Changed · -61 tokens per session c20925b58167
- 3d ago First seen · 109 lines · 105 tokens per session scan A fea3fed540f2
browser-testing is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 2d ago), licensed Apache-2.0. It adds 44 tokens to every session and 2,882 once invoked, about $0.0002 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
browser-testing
Test and debug browser code with Chrome DevTools MCP. Use when building or debugging browser UI, inspecting the DOM, capturing console errors, analyzing network requests, or verifying visual output.
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
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.
webapp-selenium-testing
Author and maintain versioned Selenium WebDriver tests with Java and JUnit 5. Use for creating, debugging, or running Selenium specs, implementing Page Objects, handling explicit waits, capturing screenshots, or setting up Maven test projects. Supports Chrome, Firefox, and Edge. Keywords: Selenium WebDriver, Java…
playwright-testing
Playwright E2E testing patterns, cross-browser configuration, page objects, and CI setup. Use when creating E2E specs, visual regression suites, or configuring Playwright in CI. Trigger terms: playwright, e2e, trace, page object, cross-browser.