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 VKirill/claude-lane-stack --skill browser-qagit clone --depth 1 https://github.com/VKirill/claude-lane-stackWrote 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/vkirill/claude-lane-stack/browser-qa)<a href="https://agentmods.dev/skills/vkirill/claude-lane-stack/browser-qa"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/browser-qa/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/vkirill/claude-lane-stack/browser-qa"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/browser-qa.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.00092 | $0.02256 |
| Opus 5.5 | $0.00037 | $0.00902 |
| Sonnet 5.5 | $0.00018 | $0.00451 |
| Haiku 4.5 | $0.00009 | $0.00226 |
Grade A, and why
browser-qa 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 12d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser QA
Adapted from lee-to/ai-factory#154
replay rules. Paths and gates are lane-stack. No .ai-factory, no human
«работает или нет».
Inside a Lane Pilot chat (
LANE_PILOT_AGENT_TYPEset / toolslane_pilot_*present) do not run this file's replay and digest procedure. The PM checks an accepted task withlane_pilot_browser_qa; the check runs in a child thread throughbb browser-automation(no MCP browser) and ends with the one fenced JSON verdict its prompt asks for, changing no files..agents/qa/replay,qa-digest,chrome-qa,browser-qa-jevandchrome-devtoolsbelow are the terminal harness. The PM does not click in its own chat.
Info
If $ARGUMENTS is exactly info, print references/info.md verbatim (Russian), then stop.
Layout
.agents/qa/context.md # cross-run, non-secret
.agents/qa/<slug>/
cases.md # source of truth for TC-*
REPORT.md # execution only; never overwrite cases
shots/
replay/TC-00N.js
replay/history/
Copy structure from references/ next to this skill. English on disk.
Chat may be Russian. Redact tokens, cookies, OTP, password, jwt → [REDACTED].
Cases
PM / SPEC acceptance → cases.md. One ## TC-00N heading per case (see
references/cases.md). Fields: Surface, Priority, Viewport, Preconditions,
Steps, Expected.
| Surface | This agent |
|---|---|
browser-ui |
Required. Live browser. Replay first. |
cli / backend-test / api |
Do not click. Note blocked: use L0/L1. No human array-checking. |
human |
Leave pending. The PM asks the operator. |
Default viewports if omitted: 375 768 1280.
Bindings
qa-digest cases .agents/qa/<slug>/cases.md
qa-digest script .agents/qa/<slug>/replay/TC-001.js
qa-digest target local 'http://127.0.0.1:5173/'
git -C . rev-parse HEAD
tree is clean if git status --porcelain has nothing except .agents/qa/;
else dirty.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago Changed · -15 lines · +18 tokens per session 9671975f2534
- 26d ago Changed 86e5760bc948
- 1mo ago Changed · +18 lines 9062939a4a9c
- 1mo ago First seen · 134 lines · 74 tokens per session scan A 0e524129f107
browser-qa is a skill published in the GitHub repository VKirill/claude-lane-stack (122 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 2,256 once invoked, about $0.0004 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-14.
Other skills, from other repositories
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.
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.
browser-use
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.
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.
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.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.