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 gabrielmoreira/agent-skills-mirror --skill browser-testing-with-screenshotsgit clone --depth 1 https://github.com/gabrielmoreira/agent-skills-mirrorWrote 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/gabrielmoreira/agent-skills-mirror/browser-testing-with-screenshots)<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/browser-testing-with-screenshots"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/browser-testing-with-screenshots/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/gabrielmoreira/agent-skills-mirror/browser-testing-with-screenshots"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/browser-testing-with-screenshots.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.00032 | $0.01891 |
| Opus 5 | $0.00016 | $0.00945 |
| Sonnet 5 | $0.00006 | $0.00378 |
| Haiku 4.5 | $0.00003 | $0.00189 |
Grade A, and why
browser-testing-with-screenshots scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Simple page content validation (use curl/wget) This is a copy
100% identical to browser-testing-with-screenshots — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Testing with Screenshots
Overview
Automate Chrome browser testing with visual verification using browser-tools. Connect to Chrome DevTools Protocol for navigation, interaction, and screenshot capture to confirm application functionality.
Prerequisites
REQUIRED: Install agent-tools from https://github.com/badlogic/agent-tools
# Clone and install agent-tools
git clone https://github.com/badlogic/agent-tools.git
cd agent-tools
# Follow installation instructions in the repository
# Ensure all executables (browser-start.js, browser-nav.js, etc.) are in your PATH
Verify installation:
# Check that browser tools are available
which browser-start.js
which browser-nav.js
which browser-screenshot.js
All browser-* commands referenced in this skill come from the agent-tools repository and must be properly installed and accessible in your system PATH.
When to Use
Use this skill when:
- Testing web application UI flows
- Verifying visual changes or layouts
- Automating repetitive browser interactions
- Documenting application behavior with screenshots
- Testing localhost applications during development
- Need to interact with elements that require human-like selection
Don't use for:
- API testing (use direct HTTP calls)
- Headless testing where visuals don't matter
- Simple page content validation (use curl/wget)
Quick Reference
| Task | Command | Purpose |
|---|---|---|
| Start browser | browser-start.js |
Launch Chrome with debugging |
| Navigate | browser-nav.js http://localhost:5172/dashboard |
Go to specific URL |
| Take screenshot | browser-screenshot.js |
Capture current viewport |
| Pick elements | browser-pick.js "Select the login button" |
Interactive element selection |
| Run JavaScript | browser-eval.js 'document.title' |
Execute code in page context |
| Extract content | browser-content.js |
Get readable page content |
| View cookies | browser-cookies.js |
List session cookies |
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.
- 7d ago First seen · 279 lines · 32 tokens per session scan A 76188cf6d9ec
browser-testing-with-screenshots is a skill published in the GitHub repository gabrielmoreira/agent-skills-mirror (17 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,891 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to browser-testing-with-screenshots, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
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.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
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.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…