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 petrkindlmann/qa-skills --skill mobile-testinggit clone --depth 1 https://github.com/petrkindlmann/qa-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/petrkindlmann/qa-skills/mobile-testing)<a href="https://agentmods.dev/skills/petrkindlmann/qa-skills/mobile-testing"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/mobile-testing.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk 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.00198 | $0.03335 |
| Opus 5 | $0.00099 | $0.01667 |
| Sonnet 5 | $0.00040 | $0.00667 |
| Haiku 4.5 | $0.00020 | $0.00333 |
Grade C, and why
mobile-testing scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -Ls "https://get.maestro.mobile.dev" | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Or the cross-platform curl one-liner: How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Route
| Situation | Go to |
|---|---|
| Picking a framework for an app type | Framework Decision |
| Native/hybrid Appium setup + selectors + gestures | Appium 3.x → references/appium-patterns.md |
| React Native suite | Detox → references/detox-and-maestro.md |
| Low-friction cross-platform YAML | Maestro → references/detox-and-maestro.md |
| Cloud device matrix (P0/P1/P2) | Device Farm → references/device-farm.md |
| Deep links, push, biometrics, offline, permissions | Mobile-Specific Patterns → references/mobile-patterns.md |
Discovery Questions
Check .agents/qa-project-context.md in the project root first — if it exists, use it and skip any question it already answers.
- App type: Native iOS/Android, React Native, Flutter, or hybrid (Cordova/Capacitor)? This picks the framework (see Framework Decision).
- Real devices or emulators? Real devices for release validation and performance; emulators/simulators for development speed. Most teams need both.
- Device farm: BrowserStack App Automate, Sauce Labs, AWS Device Farm, or self-hosted? Budget and CI integration decide.
- OS coverage: Minimum iOS and Android versions? Read analytics for actual user distribution before building the matrix — do not target the newest hardware by default.
- Existing CI pipeline: Where do mobile tests run — local machines, CI runners with emulators, or cloud device farms?
- App distribution: How are test builds distributed — TestFlight, Firebase App Distribution, direct APK/IPA? This determines how the farm gets the binary.
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.
- 8d ago First seen · 219 lines · 198 tokens per session scan C facda36464fb
mobile-testing is a skill published in the GitHub repository petrkindlmann/qa-skills (113 stars, last pushed 2mo ago), licensed MIT. It adds 198 tokens to every session and 3,335 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.
Detox Mobile Testing
Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.
Espresso Android Testing
Android UI testing with Espresso framework including view matchers, actions, assertions, idling resources, and RecyclerView testing patterns.
Flutter Testing Patterns
Flutter app testing with widget tests, integration tests, golden tests, Mockito, bloc testing, and Flutter Driver for end-to-end scenarios.
Detox React Native Testing
End-to-end testing for React Native apps using Detox with gray-box testing, synchronization, device simulation, and CI integration.
flowtest
Execute flow YAML files as end-to-end tests against web, Android, and iOS apps. Drives platform drivers (agent-browser, adb, idb) step-by-step, captures screenshots and video, and produces a structured report. Supports declarative steps (tap, type, scroll, assert, screenshot, wait) and AI-driven steps for dynamic UI…