mobile-testing

mobile-testing is a skill for Claude Code from summarybotng/summarybot-ng. It costs 49 tokens per session (1,619 once invoked), scanned A, original, MIT.

A guide to testing iOS and Android apps across different devices, operating systems, gestures, sensors, permissions, and network conditions. It covers native, hybrid, and mobile web apps.

In plain words
What is it for?
Use it to plan device coverage and check gestures, offline behavior, notifications, permissions, interruptions, and performance.
Why use it?
Mobile behavior can differ between platforms and device types, so a test that passes on one device may fail elsewhere.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to plan device coverage and check gestures, offline behavior, notifications, permissions, interruptions, and performance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/summarybotng/summarybot-ng/mobile-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 summarybotng/summarybot-ng --skill mobile-testing
Clone the repo
git clone --depth 1 https://github.com/summarybotng/summarybot-ng

Made for: Claude Code.

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 mobile-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/mobile-testing/github.svg)](https://agentmods.dev/skills/summarybotng/summarybot-ng/mobile-testing)
Your own site
<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/mobile-testing"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/mobile-testing/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.

agentmods 80×15 button for mobile-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/mobile-testing"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/mobile-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,619 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.
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.00049 $0.01619
Opus 5 $0.00024 $0.00809
Sonnet 5 $0.00010 $0.00324
Haiku 4.5 $0.00005 $0.00162

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

Security

Grade A, and why

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 5d 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.

.claude/skills/mobile-testing/SKILL.md · 226 lines

How it starts

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

Mobile Testing

<default_to_action> When testing mobile applications:

  1. DEFINE device coverage matrix (Tier 1: 60%, Tier 2: 30%, Tier 3: 10%)
  2. TEST platform differences (iOS ≠ Android: back button, permissions, UI)
  3. VALIDATE touch gestures (tap, swipe, pinch, long-press)
  4. TEST mobile-specific scenarios (offline, low battery, interruptions)
  5. USE real devices for critical paths, emulators for fast feedback

Quick Mobile Checklist:

  • Test on latest iOS + Android flagship devices
  • Test offline mode and network transitions
  • Verify push notifications work
  • Test gesture interactions (swipe, pinch)
  • Check permissions flow (camera, location, notifications)

Critical Success Factors:

  • Emulators for 80% of testing, real devices for 20% critical paths
  • Test on devices your users actually use (analytics)
  • Device fragmentation is Android's biggest challenge </default_to_action>

Quick Reference Card

When to Use

  • Native app development (iOS/Android)
  • Hybrid apps (React Native, Flutter)
  • Mobile web / PWAs
  • App store submission preparation

iOS vs Android Differences

Aspect iOS Android
OS Versions 2-3 supported 10+ in use
Devices ~40 models 1000+ variants
Back Button Gesture/nav Hardware/software
Permissions Single prompt Runtime granular
App Store Strict review Google Play + sideload

Device Coverage Tiers

Tier Coverage Devices
Tier 1 60% users iPhone 15, Galaxy S24, iPad
Tier 2 30% users iPhone 14/13, Pixel 8
Tier 3 10% users Older devices, other manufacturers

Mobile Performance Goals

Metric Target
App launch < 2 seconds
Screen transition < 300ms
Frame rate 60 FPS
Battery drain < 5%/hour background

Touch Gesture Testing

// Appium gesture examples
// Tap
await driver.touchAction({ action: 'tap', x: 100, y: 200 });

// Swipe (scroll down)
await driver.touchAction([
  { action: 'press', x: 200, y: 400 },
  { action: 'moveTo', x: 200, y: 100 },
  { action: 'release' }
]);

// Pinch to zoom
const finger1 = [
  { action: 'press', x: 100, y: 200 },
  { action: 'moveTo', x: 50, y: 150 },
  { action: 'release' }
];
const finger2 = [
  { action: 'press', x: 200, y: 200 },
  { action: 'moveTo', x: 250, y: 250 },
  { action: 'release' }
];
await driver.multiTouchAction([finger1, finger2]);

// Long press
await driver.touchAction({
  action: 'longPress',
  x: 100, y: 200,
  duration: 2000
});

Read the full file on GitHub · 226 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. 5d ago First seen · 226 lines · 49 tokens per session scan A 2abfc0211a8e

Subscribe to this mod's changes

mobile-testing is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 1,619 once invoked, about $0.0002 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-09-03.

Related

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.

PramodDutta/qaskills · 32 tokens

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.

noqa-ai/noqa · 47 tokens

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.

buiphucminhtam/forgewright · 81 tokens

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…

tai2/aco · 111 tokens

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 end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.

software-mansion/argent · 64 tokens

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.

mobile-next/mobile-mcp · 58 tokens