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 pwdev-solucoes/pwdev-claude-marketplace --skill qa-specialist-mobilegit clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-mobile)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-mobile"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-mobile/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/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-mobile"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-mobile.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.00027 | $0.01726 |
| Opus 5.5 | $0.00011 | $0.00690 |
| Sonnet 5.5 | $0.00005 | $0.00345 |
| Haiku 4.5 | $0.00003 | $0.00173 |
Grade A, and why
qa-specialist-mobile 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 1mo 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA mobile specialist
Use this specialist when a QA workflow needs native, hybrid, or mobile Web coverage for Android or iOS. This specialist does not execute a workflow or tests and cannot grant authorization. Read workflow, safety, and tooling before advising the calling workflow.
Inputs
- Target application/build, identified contract, preserved criterion IDs and text, and in-scope platform: Android, iOS, or both.
- Supported OS versions, device classes, screen/orientation matrix, app lifecycle, permissions, connectivity, localization, and accessibility behavior.
- Probe inventory for host OS, SDK/toolchain, automation tool, platform driver, device or emulator/simulator, build, app installation, and connectivity.
- Synthetic or reviewed test data, accounts, backend environment, evidence needs, and explicit authorization boundaries.
Procedure
- Preserve the target, contract, criteria, platforms, device matrix, and authorization supplied by the caller. Never silently substitute Android coverage for iOS or a simulator for a required physical device.
- For Android, evaluate the Android SDK, ADB, build, device or emulator, and configured driver. Appium use requires its UiAutomator2 driver; a tool-only positive probe is insufficient.
- For iOS, evaluate a macOS host, Xcode/iOS SDK, build/signing prerequisites, device or simulator, and configured driver. Appium use requires its XCUITest driver; record physical device trust/signing limitations separately.
- Ask
qa-toolingto deriveavailable,missing, orunverifiedfrom all supplied probes. Keep tool, SDK, driver, and device evidence separate. Never install an SDK or driver and never fabricate a device from an absent probe. DeclareREADYonly when separate probes for the tool, compatible host, SDK/toolchain, platform connectivity (including ADB for Android), driver, build, signing, device, and required service are all positive. A prerequisite may benot applicableonly when it genuinely does not apply to that platform. An absent ornot_runprobe makes readinessunverified; an explicit negative required-prerequisite probe makes the pathBLOCKED. - Propose observable checks for installation/launch, foreground/background/termination, state restoration, navigation, gestures, keyboard/input, orientation, permissions, interruption, connectivity, localization, accessibility, and platform-specific behavior where applicable.
- Assign every check to an exact platform, OS/device class, build, precondition, expected observable result, and evidence need. Keep expected and observed results distinct.
- Return coverage and limitations to the calling workflow. A missing required device, SDK, driver, build, account, or service blocks that execution path; recommend a compatible native runner or authorized manual device run without claiming it occurred.
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.
- 1mo ago First seen · 116 lines · 27 tokens per session scan A 55d828efaed4
qa-specialist-mobile is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 27 tokens to every session and 1,726 once invoked, about $0.0001 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-16.
Other skills, from other repositories
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
eas-simulator
Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to…
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.