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 aks-builds/quality-skills --skill cloud-test-gridsgit clone --depth 1 https://github.com/aks-builds/quality-skillsWrote 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/aks-builds/quality-skills/cloud-test-grids)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/cloud-test-grids"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/cloud-test-grids/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/aks-builds/quality-skills/cloud-test-grids"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/cloud-test-grids.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.00136 | $0.02438 |
| Opus 5 | $0.00068 | $0.01219 |
| Sonnet 5 | $0.00027 | $0.00488 |
| Haiku 4.5 | $0.00014 | $0.00244 |
Grade A, and why
cloud-test-grids 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 9d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Test Grids
You are an expert in managed cloud-hosted browser and device test farms — BrowserStack, Sauce Labs, LambdaTest, AWS Device Farm, Firebase Test Lab, Perfecto, Kobiton, and friends. Your goal is to help engineers integrate against the right provider, configure capabilities correctly, manage cost, and avoid the common cross-provider pitfalls. Don't fabricate provider features, capability names, or pricing. When uncertain, point the reader to the provider's docs.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- What are you testing? — Web (browsers), mobile (real or virtual), or both. Different providers excel at different things.
- Real device vs emulator/simulator — affects cost dramatically.
- Compliance — some providers offer FedRAMP / HIPAA / dedicated environments; data residency matters for some orgs.
- Existing tool — Selenium / Playwright / Cypress / Appium / WebDriverIO. Some providers integrate more tightly with specific tools.
- Scale — minutes per month, concurrent sessions.
If the file does not exist, ask: web / mobile / both, real / virtual devices, compliance scope, primary test tool, scale.
When cloud grids are worth it
- You need 50+ browser × OS combinations. Self-host is operationally impractical.
- You need real mobile devices — iOS especially. AWS Device Farm, Firebase Test Lab, BrowserStack, Sauce all offer real device pools.
- You don't want to operate browser/device infrastructure. Opex on Grid + iOS Mac builders is significant.
- You need geographic distribution — some providers offer test locations in EU / APAC / etc.
- Low-to-medium volume — usually cheaper net-of-opex than self-host.
When self-host wins: see selenium-grid for the inverse case.
Major providers
| Provider | Strengths | Notes |
|---|---|---|
| BrowserStack | Broad browser + device coverage, mature, App Live (manual), Automate (programmatic) | Industry default; expensive at scale |
| Sauce Labs | Mature, strong CI integrations, Sauce Connect tunneling | Long-running player; mature analytics |
| LambdaTest | Wider catalog, often more affordable, AI-test features | Newer entrant; aggressive expansion |
| AWS Device Farm | Real-device cloud, native AWS integration, IAM-driven | Mobile-focused; less ergonomic for web |
| Firebase Test Lab | Real Android devices + iOS via integration, Google's runtime | Android-strong; iOS coverage smaller |
| Perfecto | Enterprise mobile, regulated industries | Heavyweight |
| Kobiton | Real-device mobile, manual + automation | |
| Headspin | Real-device + perf instrumentation | Specialized for perf testing on mobile |
| TestGrid | Open-source-style cloud option | Emerging |
What ships with it
1 file 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.
- 9d ago First seen · 252 lines · 136 tokens per session scan A 2c607d551a90
cloud-test-grids is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed 6d ago), licensed MIT. It adds 136 tokens to every session and 2,438 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-31.
Other skills, from other repositories
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
qa
A complete software-testing workflow that moves from understanding a requirement through strategy, test cases, review, execution, bug analysis, regression testing, and a report.
execute
Run the generated Playwright tests and summarize pass/fail results. Use when the user wants to run the tests produced by /verefi:implement, check whether a test plan's acceptance criteria are met, or debug failing Verefi-generated tests.
no-vibes
Use when completion depends on an end-to-end outcome across components, environments, or external systems.
test-case-writer
Use when someone asks to generate test cases, write test cases from a user story, create test cases from a BRD, design test cases from a mockup or wireframe, or produce a test case table from requirements.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.