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 agentmods add skills/pramoddutta/qaskills/browserstack-testingnpx skills add PramodDutta/qaskills --skill browserstack-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/browserstack-testing)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/browserstack-testing"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/browserstack-testing.svg" alt="Measured on agentmods" 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 | $0.00044 | $0.04202 |
| Opus 5 | $0.00022 | $0.02101 |
| Sonnet 5 | $0.00009 | $0.00840 |
| Haiku 4.5 | $0.00004 | $0.00420 |
Grade A, and why
BrowserStack Cloud 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 today.
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 — 540 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BrowserStack Cloud Testing Skill
You are an expert in BrowserStack cloud testing platform. When the user asks you to set up cross-browser testing, configure BrowserStack Automate with Playwright or Selenium, implement Percy visual testing, or optimize cloud test execution, follow these detailed instructions.
Core Principles
- Capability-driven browser selection -- Define browser and device capabilities precisely. Use BrowserStack's capability generators to avoid configuration errors.
- Parallel execution optimization -- Maximize parallel test sessions to reduce total execution time. Design tests for independence to enable safe parallelization.
- Local testing for pre-deployment -- Use BrowserStack Local to test staging environments and localhost applications through a secure tunnel before deploying to production.
- Visual regression with Percy -- Integrate Percy snapshots into existing Playwright or Selenium tests for automated visual comparison across browsers and viewports.
- Observability for debugging -- Enable BrowserStack Observability to get AI-powered failure analysis, flaky test detection, and performance insights without additional instrumentation.
- Network and geolocation simulation -- Use BrowserStack's network throttling and geolocation capabilities to test under realistic conditions for global users.
- Cost-efficient test distribution -- Balance test coverage across browsers and devices based on analytics data. Test the top 80% of user configurations, not every possible combination.
Project Structure
browserstack-tests/
config/
browserstack.config.ts
capabilities.ts
local-config.ts
tests/
e2e/
login.spec.ts
checkout.spec.ts
search.spec.ts
visual/
homepage-visual.spec.ts
product-page-visual.spec.ts
mobile/
mobile-navigation.spec.ts
mobile-checkout.spec.ts
helpers/
browserstack-client.ts
local-tunnel.ts
capability-builder.ts
percy/
percy-config.ts
snapshot-helpers.ts
scripts/
run-parallel.sh
check-session-status.ts
reports/
.gitkeep
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.
- today First seen · 540 lines · 44 tokens per session scan A c7aed7f2c96b
BrowserStack Cloud Testing is a skill published in the GitHub repository PramodDutta/qaskills (214 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 4,202 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-09-03.
Other skills, from other repositories
compatibility-testing
Cross-browser, cross-platform, and cross-device compatibility testing ensuring consistent experience across environments. Use when validating browser support, testing responsive design, or ensuring platform compatibility.
cdp
Drive Browser Use Desktop's assigned Chromium target via the DevTools Protocol from JavaScript. Run snippets through the bundled browser-harness-js CLI; it auto-spawns a long-lived Bun HTTP server holding a CDP Session, and every call executes against the same persistent connection.
browser-automation
Web automation with 4-layer escalation (Fetch, Genesis Browser, On-Demand MCP, Computer Use), anti-detection, and persistent profiles.
evoui-browser
Use Evoui Browser as the default entry point for common, self-terminating web tasks that need a real browser through agent-browser, including navigation, page reading, clicks, forms, login flows, screenshots, web testing, and browser automation. Managed tasks record evidence from the first run for possible reuse. Also…
cross-browser-typography-qa
Use this skill when web text looks clipped, flattened, wrapped incorrectly, misaligned, or materially different between Chromium and WebKit/Safari. Treat text rendering as both a geometry problem and a visual paint problem: passing DOM bounds does not prove that every glyph is intact.
otel-browser
OpenTelemetry browser/RUM mechanics for SPAs and MPAs. Use for “browser OTel,” “frontend observability,” “Web Vitals,” sdk-trace-web, WebTracerProvider, browser-sdk, browser instrumentations, page-load or route tracing, sessions, clicks, console capture, JavaScript errors, or frontend-to-backend trace correlation.…