cross-browser-testing

cross-browser-testing is a skill for Claude Code, Codex from petrkindlmann/qa-skills. It costs 131 tokens per session (3,972 once invoked), scanned A, original, MIT.

A testing guide for checking whether a website works across different browsers, devices, and operating systems. It covers choosing browsers from usage data and running tests locally or through cloud services.

In plain words
What is it for?
Use it to design browser test lists, configure Playwright or cloud browser services, test Safari and Windows, validate progressive enhancement, and document browser-specific issues.
Why use it?
It helps find browser-specific CSS and JavaScript problems before users do, while avoiding tests for browsers nobody uses. It also records known differences so they are not investigated repeatedly.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to design browser test lists, configure Playwright or cloud browser services, test Safari and Windows, validate progressive enhancement, and document browser-specific issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/petrkindlmann/qa-skills/cross-browser-testing
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.

Any agent
npx skills add petrkindlmann/qa-skills --skill cross-browser-testing
Clone the repo
git clone --depth 1 https://github.com/petrkindlmann/qa-skills

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 cross-browser-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/cross-browser-testing.svg)](https://agentmods.dev/skills/petrkindlmann/qa-skills/cross-browser-testing)
Your own site
<a href="https://agentmods.dev/skills/petrkindlmann/qa-skills/cross-browser-testing"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/cross-browser-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 131 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,972 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. Third-party audits
  • Socket pass 11 May 2026
  • Snyk pass 11 May 2026
How audits are shown
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.1 $0.00131 $0.03972
Opus 5 $0.00066 $0.01986
Sonnet 5 $0.00026 $0.00794
Haiku 4.5 $0.00013 $0.00397

Measured 8d ago against content hash fc26ccd87643, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

cross-browser-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 8d 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/cross-browser-testing/SKILL.md · 234 lines

How it starts

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

Quick Route

Situation Go to
Need to decide which browsers to test Browser Matrix Design
Already on Playwright, just add browsers Playwright Browser Configuration → references/playwright-and-cloud-config.md
Need real Safari/Windows/older OS, not engines Cloud Platform Setup
One browser misbehaves; want a test for it Common Cross-Browser Issues + browserName branch in references/testing-patterns.md
Need to record a divergence so it is not re-debugged Known-Issues Log
Pixel diffs / baseline thresholds use visual-testing

Discovery Questions

Check .agents/qa-project-context.md first — if it exists, use it and skip anything already answered there. Then:

  1. Target browsers from analytics: What do actual users use? Pull browser/OS data from your analytics tool. Testing browsers nobody uses is waste; missing a browser 15% of users rely on is a bug.
  2. Desktop and mobile? Mobile Safari on iOS and Chrome on Android render differently than their desktop counterparts. Treat them as separate matrix entries.
  3. Cloud platform: BrowserStack, Sauce Labs, LambdaTest, or local engines only? Cloud platforms provide real branded browsers and OSes; Playwright's bundled engines cover Chromium, Firefox, and WebKit (not Chrome/Safari themselves).
  4. Progressive enhancement or pixel-perfect? Progressive enhancement accepts graceful degradation. Pixel-perfect demands identical rendering. The answer determines pass/fail criteria.
  5. Existing Playwright config? If the project already uses Playwright, cross-browser testing is a configuration change, not a new tool.

Read the full file on GitHub · 234 lines

Files

What ships with it

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

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. 8d ago First seen · 234 lines · 131 tokens per session scan A fc26ccd87643

Subscribe to this mod's changes

cross-browser-testing is a skill published in the GitHub repository petrkindlmann/qa-skills (113 stars, last pushed 2mo ago), licensed MIT. It adds 131 tokens to every session and 3,972 once invoked, about $0.0007 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-30.

Related

Other skills, from other repositories

Console Error Hunter

Systematically detect, capture, and categorize browser console errors, warnings, and unhandled exceptions during automated test execution.

PramodDutta/qaskills · 26 tokens

Geb Testing

Browser automation testing with Geb framework for Groovy/JVM using jQuery-like content DSL, Page Object pattern, Spock integration, and WebDriver abstraction.

PramodDutta/qaskills · 34 tokens

playwright-e2e

Comprehensive end-to-end testing skill using Playwright for web applications, covering page objects, selectors, assertions, waits, fixtures, and test organization.

PramodDutta/qaskills · 36 tokens

e2e-testing-claude-code

Make Claude Code write and maintain end-to-end tests like a senior SDET — Playwright and Cypress flows with stable locators, the Page Object Model, fixtures, reused auth state, network mocking, and flake-free CI. Claude Code E2E testing, done right.

PramodDutta/qaskills · 65 tokens

Browser Agent QA Testing

Teach agents to use AI browser agents for exploratory and smoke QA with step budgets, evidence-based assertions, guardrails, and Playwright conversion.

PramodDutta/qaskills · 33 tokens

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…

katalon-labs/true-skills · 122 tokens