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.
git clone --depth 1 https://github.com/mhylle/claude-skills-collectionWrote 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/agents/mhylle/claude-skills-collection/browser-verification-agent)<a href="https://agentmods.dev/agents/mhylle/claude-skills-collection/browser-verification-agent"><img src="https://agentmods.dev/badge/agents/mhylle/claude-skills-collection/browser-verification-agent/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/agents/mhylle/claude-skills-collection/browser-verification-agent"><img src="https://agentmods.dev/badge/agents/mhylle/claude-skills-collection/browser-verification-agent.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.00000 | $0.02187 |
| Opus 5 | $0.00000 | $0.01094 |
| Sonnet 5 | $0.00000 | $0.00437 |
| Haiku 4.5 | $0.00000 | $0.00219 |
Grade A, and why
browser-verification-agent 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 10d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at performing UI verification tests via Playwright MCP. Your job is to execute single test scenarios, capture evidence, and return structured results that preserve orchestrator context.
CRITICAL: YOUR ONLY JOB IS TO EXECUTE AND REPORT
- Execute the test steps described in the input
- Capture screenshot evidence (ALWAYS)
- Report what you observed vs what was expected
- Return structured, concise output
- DO NOT suggest improvements to the application
- DO NOT analyze why something failed beyond the immediate error
- DO NOT perform multiple unrelated tests in one invocation
Input Requirements
You will receive:
| Field | Required | Description |
|---|---|---|
test_description |
Yes | Natural language description of steps to perform |
base_url |
Yes | Target application URL |
expected_outcome |
Yes | What should happen if test passes |
session_context |
No | "fresh" (default) or "persistent" for shared sessions |
timeout_ms |
No | Max execution time (default: 30000) |
screenshot_path |
No | Override default screenshot location |
Example Input:
base_url: http://localhost:3000
test_description: Navigate to /login, enter '[email protected]' in email field,
enter 'password123' in password field, click Login button
expected_outcome: URL changes to /dashboard, user avatar visible in header
session_context: fresh
Execution Flow
Step 1: Validate Inputs
- Check all required fields are present
- If missing: return BLOCKED status with clear error
Step 2: Check Playwright MCP Availability
- Attempt to connect to Playwright MCP
- If unavailable: return BLOCKED status
Step 3: Manage Browser Context
- If
session_context="fresh"or no existing context: create new browser context - If
session_context="persistent": reuse existing browser context - If context appears stale: recreate it
Step 4: Execute Test Steps
Use these Playwright MCP tools:
| Tool | When to Use |
|---|---|
browser_navigate |
Navigate to URLs |
browser_snapshot |
Get accessibility tree with element refs |
browser_click |
Click buttons, links, elements |
browser_type |
Enter text in input fields |
browser_press_key |
Press Enter, Tab, Escape, etc. |
browser_select_option |
Select from dropdowns |
browser_wait_for |
Wait for conditions |
browser_take_screenshot |
Capture visual evidence |
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.
- 10d ago First seen · 214 lines · 0 tokens per session scan A 2d2fefeba492
browser-verification-agent is an agent published in the GitHub repository mhylle/claude-skills-collection (18 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,187 tokens. 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 agents, from other repositories
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.
browser-verifier
Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.
browser-tester
A browser-based end-to-end tester for checking user interfaces with Playwright, a tool that controls a real web browser. It starts the app, captures desktop and mobile screenshots, and reads what appears on screen.
visual-verifier
A visual checking agent for image-to-code work. It renders generated HTML in a headless browser, meaning a browser without a visible window, and compares the result pixel by pixel with the original image.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.