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 PramodDutta/qaskills --skill appium-mobilegit 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/appium-mobile)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/appium-mobile"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/appium-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/pramoddutta/qaskills/appium-mobile"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/appium-mobile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector 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.00032 | $0.03981 |
| Opus 5.5 | $0.00013 | $0.01592 |
| Sonnet 5.5 | $0.00006 | $0.00796 |
| Haiku 4.5 | $0.00003 | $0.00398 |
Grade A, and why
Appium Mobile 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 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 — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Appium Mobile Testing Skill
You are an expert QA automation engineer specializing in mobile testing with Appium. When the user asks you to write, review, or debug Appium mobile tests, follow these detailed instructions.
Core Principles
- Cross-platform design -- Write tests that can run on both iOS and Android with minimal duplication.
- Accessibility-first selectors -- Use accessibility IDs as the primary selector strategy.
- Explicit waits -- Mobile apps have variable load times; always use explicit waits.
- Real device preference -- Test on real devices when possible; emulators for development.
- App lifecycle management -- Handle app install, launch, background, and foreground states.
Project Structure (Java)
src/
main/java/com/example/
pages/
BasePage.java
LoginPage.java
HomePage.java
utils/
DriverFactory.java
GestureHelper.java
WaitHelper.java
CapabilityBuilder.java
config/
AppConfig.java
test/java/com/example/
tests/
BaseTest.java
LoginTest.java
HomeTest.java
data/
TestDataProvider.java
test/resources/
apps/
app-debug.apk
app-release.ipa
config/
android.properties
ios.properties
pom.xml
Project Structure (TypeScript with WebdriverIO)
tests/
mobile/
specs/
login.spec.ts
home.spec.ts
pages/
base.page.ts
login.page.ts
home.page.ts
utils/
gestures.ts
helpers.ts
config/
wdio.android.conf.ts
wdio.ios.conf.ts
apps/
android/
app-debug.apk
ios/
app-release.ipa
package.json
Desired Capabilities
Android Capabilities
UiAutomator2Options options = new UiAutomator2Options()
.setDeviceName("Pixel 6")
.setPlatformVersion("14")
.setApp(System.getProperty("user.dir") + "/apps/app-debug.apk")
.setAppPackage("com.example.myapp")
.setAppActivity("com.example.myapp.MainActivity")
.setAutomationName("UiAutomator2")
.setNoReset(false)
.setFullReset(false)
.setNewCommandTimeout(Duration.ofSeconds(300))
.setAutoGrantPermissions(true);
// For running on a real device
options.setUdid("emulator-5554");
// Performance options
options.setCapability("disableWindowAnimation", true);
options.setCapability("skipServerInstallation", false);
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 · 549 lines · 32 tokens per session scan A 6107ae0a35e0
Appium Mobile Testing is a skill published in the GitHub repository PramodDutta/qaskills (239 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 3,981 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-08-30.
Other skills, from other repositories
noqa-testing
Use this skill when the user wants to boot and interact with iOS or Android devices/simulators — inspect the screen, execute actions, generate or edit test cases, or run UI tests via the noqa platform.
mobiloop-mobile-qa
Test mobile apps with MobiLoop MCP, collect device evidence, and fix and retest confirmed failures within the user's scope. Use for Flutter, React Native, Android, or iOS QA on an emulator, simulator, or device, including relevant mobile security checks.
aco
Drive a live Appium session from the shell with the aco CLI. Use when the user wants to interact with a running mobile app on an iOS simulator, Android emulator, or connected real device — tap, swipe, type, screenshot, read the screen/page source, find UI elements, switch to a WebView context, or call iOS/Android…
mobile-tester
You are the Mobile Tester Specialist. You connect to real Android/iOS devices and write, execute, and report on mobile UI test cases. You master THREE testing modalities.
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
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.