browser-test-executor

browser-test-executor is a skill for Claude Code, Codex from dangnhit/qa-tester. It costs 38 tokens per session (858 once invoked), scanned A, original, Apache-2.0.

A controlled browser-test runner for approved, bounded test cases. It uses fresh isolated browser sessions and records attempts so results can be checked later.

In plain words
What is it for?
Use it for browser tests, reruns, regression checks, and diagnosing blocked test execution. It is intended for committed test cases rather than ad-hoc browser control.
Why use it?
It provides repeatable browser-test results without mixing them with other kinds of testing. It also reports when a browser test cannot run under the required rules.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/dangnhit/qa-tester/browser-test-executor
Any agent
npx skills add dangnhit/qa-tester --skill browser-test-executor
Clone the repo
git clone --depth 1 https://github.com/dangnhit/qa-tester

Made for: Claude Code, Codex.

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.

agentmods badge for browser-test-executor

README.md
[![agentmods](https://agentmods.dev/badge/skills/dangnhit/qa-tester/browser-test-executor.svg)](https://agentmods.dev/skills/dangnhit/qa-tester/browser-test-executor)
Your own site
<a href="https://agentmods.dev/skills/dangnhit/qa-tester/browser-test-executor"><img src="https://agentmods.dev/badge/skills/dangnhit/qa-tester/browser-test-executor.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 858 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.00858
Opus 5 $0.00019 $0.00429
Sonnet 5 $0.00008 $0.00172
Haiku 4.5 $0.00004 $0.00086

Measured 3d ago against content hash 9d297458df7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

browser-test-executor 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 3d 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.

skills/browser-test-executor/SKILL.md · 38 lines

What it actually says

Browser test executor

Execution kind: runtime-backed. Read browser adapters, safety, artifact contracts, and recovery. Invoke the runtime; do not drive a browser through arbitrary JavaScript, XPath, or untyped shell commands.

This skill owns the browser Execution Surface only. Five of the remaining six — api, unit, integration, performance, security — are reached by observing a committed external suite: see observed execution for qa-skill execute playwright, the in-spec identity tag it requires, and what the git anchor refuses. A spec tagged browser there is refused and sent back here, because a Playwright JSON report names neither the engine nor the viewport a browser result must record. The seventh, manual, has no executor in either lane — no attempt is ever produced on that surface, so nothing ever executes one. Whether such an obligation can be satisfied at all turns on its accessibilityMethod, not on its surface, and those are separate axes: an obligation declaring keyboard, screen-reader or cognitive-manual is an Accessibility Obligation that a person closes with qa-skill attestation record, on whatever surface it happens to declare. One declaring no method stays explicitly unmet and cannot be attested at all — the attestation contract admits only those three methods and requires the obligation to declare the same one.

Resolve ./node_modules/.bin/qa-skill before qa-skill on PATH. Stop if neither is compatible; never use remote npx.

Example — full-workflow run producing this skill's registered attempts:

QA_SKILL="${PWD}/node_modules/.bin/qa-skill"; [ -x "$QA_SKILL" ] || QA_SKILL="$(command -v qa-skill)" || exit 1
"$QA_SKILL" runtime verify --range ">=1.0.0 <2.0.0"
SOURCE_RUN_ID="$("$QA_SKILL" workflow bootstrap --root . --environment-file environment.json --requirement-file drafts/requirements.json --plan-file drafts/plan.json --test-case-file drafts/case.json --coverage-file drafts/coverage.json | node -p 'JSON.parse(require("fs").readFileSync(0, "utf8")).runId')"
"$QA_SKILL" workflow scaffold --root . --mode execute --output execute-workflow.json --source-root . --source-run-id "$SOURCE_RUN_ID"
"$QA_SKILL" workflow run --input execute-workflow.json

PowerShell:

$QaSkill = Join-Path $PWD "node_modules/.bin/qa-skill.cmd"
if (-not (Test-Path $QaSkill)) { $QaSkill = (Get-Command qa-skill -ErrorAction Stop).Source }
& $QaSkill runtime verify --range ">=1.0.0 <2.0.0"
$Bootstrap = (& $QaSkill workflow bootstrap --root . --environment-file environment.json --requirement-file drafts/requirements.json --plan-file drafts/plan.json --test-case-file drafts/case.json --coverage-file drafts/coverage.json | ConvertFrom-Json)
& $QaSkill workflow scaffold --root . --mode execute --output execute-workflow.json --source-root . --source-run-id $Bootstrap.runId
& $QaSkill workflow run --input execute-workflow.json

Expected outputs are registered test-result attempts and evidence or gaps. Example — full run: scaffold full-workflow.json from the same captured source run ID, then run it.

Example — full run: pass registered attempts and runtime evidence to qa-report-generator after --profile full validates.

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.

  1. 3d ago First seen · 38 lines · 38 tokens per session scan A 9d297458df7c

Subscribe to this mod's changes

browser-test-executor is a skill published in the GitHub repository dangnhit/qa-tester (2 stars, last pushed 24d ago), licensed Apache-2.0. It adds 38 tokens to every session and 858 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-08-31.

Related

Other skills, from other repositories

qawolf-cli

Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…

qawolf/cli · 118 tokens

e2e-setup

Set up Playwright e2e automation tailored to this team and app. Probes the running app (auth mechanism, API surface, spec availability), interviews with recommendations instead of open questions, scaffolds the playwright/ folder, and records every decision in playwright/AUTOMATION.md for the other e2e skills to read.…

TimothyHan/qa-buddy-skills · 152 tokens

verify-fix

Re-test a bug fix after a developer resolves it. Pulls the original bug from Jira, re-executes the repro steps in the browser, checks for regressions, and updates the bug status. The final step in the SDT workflow before a ticket moves to Done. Use when: "verify fix", "retest", "is this fixed?", "check BUG-123"…

TimothyHan/qa-buddy-skills · 116 tokens

e2e-write

Write the e2e test suite from test cases: API client for preconditions, fixtures, and intent-only specs on top of a proven POM. Never invents locators — if a page has no POM, it invokes /qa-e2e-pom first. Done only when the suite passes three gates: green, green again (cleanup proof), and green under --repeat-each=3…

TimothyHan/qa-buddy-skills · 174 tokens

pw-playwright-fieldkit

Explore, debug, audit, compare, record, and test live websites with deterministic Playwright scripts and QE workflows. Use for requests to map a site, find broken pages or links, reproduce browser bugs, discover hidden or role-gated features, audit accessibility/performance, compare crawls, design or review test cases…

jpbaking/playwright-fieldkit · 143 tokens

qa

SDT test execution skill. Executes test cases from the knowledge base, verifies acceptance criteria in the browser, files bugs in Jira for failures, and updates the KB with results. Works within sprint context: knows the ticket, the ACs, the test cases, and what needs to pass before the ticket moves forward. Optional…

TimothyHan/qa-buddy-skills · 145 tokens