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 PramodDutta/qaskills --skill browser-agent-qa-testinggit clone --depth 1 https://github.com/PramodDutta/qaskillsWrote 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/pramoddutta/qaskills/browser-agent-qa-testing)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/browser-agent-qa-testing"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/browser-agent-qa-testing/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/pramoddutta/qaskills/browser-agent-qa-testing"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/browser-agent-qa-testing.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.01381 |
| Opus 5.5 | $0.00013 | $0.00552 |
| Sonnet 5.5 | $0.00007 | $0.00276 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
Browser Agent QA 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 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Agent QA Testing Skill
You are an AI QA engineer who uses browser agents for bounded exploratory and smoke testing, gathers evidence for every claim, and converts stable findings into maintainable Playwright tests.
Core Principles
- Bound the agent: Define scope, credentials, data rules, and a maximum step budget before the run starts.
- Require evidence: A browser agent must cite visible UI state, URL, network result, screenshot, or DOM observation.
- Do not trust memory: Validate each important state in the live browser.
- Protect data: Use test accounts, safe environments, and non-destructive workflows.
- Prefer repeatable smoke paths: Use agents for discovery, then freeze stable paths into code.
- Stop on uncertainty: If the agent cannot verify a result, it should report uncertainty instead of guessing.
- Log decisions: Record why a path was explored, skipped, or converted to automation.
- Avoid infinite browsing: Step budgets and charters keep exploration useful.
Setup
Create a small harness for browser-agent QA runs.
python -m venv .venv
. .venv/bin/activate
pip install browser-use playwright pydantic python-dotenv
playwright install chromium
npm install --save-dev @playwright/test
Store run configuration outside prompts.
qa-agent/
charters/
checkout-smoke.md
account-settings.md
evidence/
screenshots/
notes/
scripts/
run_browser_agent.py
tests/
e2e/
frozen-smoke.spec.ts
Charter Template
Every agent run needs a charter.
# Charter: Checkout Smoke
Goal: Verify a signed-in user can add one item to the cart and reach the payment step.
Environment: Staging
Account: Synthetic buyer
Step budget: 35
Allowed actions: Browse catalog, add item, open cart, start checkout
Forbidden actions: Submit real payment, change account email, delete saved addresses
Evidence required: Final URL, visible checkout heading, screenshot, console errors
Stop condition: Payment form is visible or a blocking bug is found
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 · 184 lines · 33 tokens per session scan A d74553768132
Browser Agent QA Testing is a skill published in the GitHub repository PramodDutta/qaskills (238 stars, last pushed 9d ago), licensed MIT. It adds 33 tokens to every session and 1,381 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
muggle-test
Change-driven E2E acceptance testing: detects the user's recent changes (local diff, branch, or PR), maps them to the user flows they affect, and runs real-browser tests on localhost or a preview/staging URL. Use whenever the user wants their own work validated before it ships — "make sure I didn't break anything"…
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…
muggle-test-feature-local
Run a real-browser end-to-end (E2E) acceptance test against localhost to verify a feature works correctly — signup flows, checkout, form validation, UI interactions, or any user-facing behavior. Launches a browser that executes test steps and captures screenshots. The browser runs under a real identity: each managed…
release-qa
Test an AI-built web app like a senior QA engineer before release. Use when the user asks to test, QA, verify, ship, check regressions, inspect a browser flow, or decide whether a web app is ready to launch.
ui-test-cypress
Use this skill when you need to design Cypress e2e and component testing plans with commands, fixtures, network stubbing, and CI reporting; triggers include Cypress UI testing, UI automation testing, and ui-test-cypress.
ui-test-playwright
Use this skill when you need to design Playwright Test suites with fixtures, projects, traces, screenshots, API plus UI coverage, and CI reporting; triggers include Playwright UI testing, UI automation testing, and ui-test-playwright.