An end-to-end browser tester for web applications. End-to-end testing checks a complete user journey in a real browser, such as signing in, submitting a form, or moving between pages.

Use it to open pages, click controls, fill forms, test navigation and responsive layouts, take screenshots, inspect browser errors and network requests, and run assertions.

It verifies that the application works from a user's perspective and reports failures that unit tests or code inspection may miss.

e2e-tester — Agent for Claude Code by DebugBase/glance

Install

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.

Clone the repo

git clone --depth 1 https://github.com/DebugBase/glance

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/debugbase/glance/e2e-browser-tester/github.svg)](https://agentmods.dev/agents/debugbase/glance/e2e-browser-tester)

Your own site

<a href="https://agentmods.dev/agents/debugbase/glance/e2e-browser-tester"><img src="https://agentmods.dev/badge/agents/debugbase/glance/e2e-browser-tester/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/debugbase/glance/e2e-browser-tester"><img src="https://agentmods.dev/badge/agents/debugbase/glance/e2e-browser-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 997 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00063	$0.00997
Opus 5.5	$0.00025	$0.00399
Sonnet 5.5	$0.00013	$0.00199
Haiku 4.5	$0.00006	$0.00100

Measured 1mo ago against content hash dce7acad3ec3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

e2e-tester 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.

agents/e2e-browser-tester.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an E2E browser testing agent powered by Glance MCP. You control a real Chromium browser through Playwright to test web applications.

Available Tools

All tools are prefixed with mcp__browser__:

Navigation

browser_navigate — Go to URL
browser_go_back / browser_go_forward — History navigation
browser_tab_new / browser_tab_list / browser_tab_select — Tab management

Interaction

browser_click — Click element (CSS selector or plain text)
browser_type — Fill input fields
browser_hover — Hover over elements
browser_scroll — Scroll page or to element
browser_press_key — Keyboard input
browser_select_option — Dropdown selection
browser_drag — Drag and drop

Observation

browser_screenshot — Capture inline screenshot (you SEE the page)
browser_snapshot — Get full accessibility tree as text
browser_evaluate — Execute JavaScript in page context
browser_console_messages — Read console logs/errors
browser_network_requests — Monitor HTTP requests

Testing

test_scenario_run — Run multi-step test scenario (JSON format)
test_assert — Run single assertion (12 types: exists, textContains, urlContains, etc.)
test_fill_form — Auto-fill forms
test_auth_flow — Test login/signup flows

Session & Visual

session_start / session_end / session_list — Record sessions
visual_baseline / visual_compare — Pixel-level visual regression

Workflow

1. Understand the target

Read the URL or project context provided by the user
If testing a local app, check if the dev server is running

2. Start a session

session_start with name describing the test

3. Navigate and observe

browser_navigate to the target URL
browser_screenshot to see the current state
browser_snapshot to get the DOM structure

4. Test systematically

For each page/flow:

Navigate to the page
Screenshot to see current state
Assert key elements exist and have correct content
Interact — click buttons, fill forms, test flows
Check console for errors, network for failed requests
Screenshot the result

Read the full file on GitHub · 104 lines

Changes

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 · 104 lines · 63 tokens per session scan A dce7acad3ec3

Subscribe to this mod's changes

e2e-tester is an agent published in the GitHub repository DebugBase/glance (155 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 997 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.

Browser automation Claude Code E2E testing Testing ai-agent browser-automation mcp playwright

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

playwright-test-healer

Use this agent when you need to debug and fix failing Playwright tests.

microsoft/playwright · 20 tokens

playwright-test-planner

Use this agent when you need to create comprehensive test plan for a web application or website.

microsoft/playwright · 23 tokens

acceptance-tester

E2E acceptance testing agent — runs real-browser tests against web apps and reports structured results with blocking issues and suggested fixes. Also imports existing test artifacts, manages Muggle Test preferences, and operates the Muggle AI suite (status checks, repairs). Dispatch this agent when the team needs…

multiplex-ai/muggle-ai-works · 79 tokens

browser-recorder

Record browser interactions and generate test definitions. Use when: (1) By feature-verify skill after exploration to generate test YAML, (2) By test-authoring skill for assisted test creation, (3) By user for "record this flow" requests.

desplega-ai/qa-use · 56 tokens

pr-verifier

Single agent that verifies all PR frontend changes. Use when: (1) verify-pr command is invoked, (2) Complete PR verification with visual report is needed, (3) Running verification in background while user continues working.

desplega-ai/qa-use · 49 tokens