gem-mobile-tester

gem-mobile-tester is an agent for Claude Code from github/awesome-copilot. It costs 22 tokens per session (870 once invoked), scanned A, original, MIT.

A mobile end-to-end testing agent for Detox, Maestro, and iOS or Android simulators, emulators, and devices. End-to-end tests check complete user flows across a running mobile app.

In plain words
What is it for?
Use it to test mobile launches, gestures, lifecycle behavior, push notifications, device-specific behavior, performance, and visual layouts.
Why use it?
It removes the need to manually launch apps and repeat mobile interaction checks across supported platforms. It also records only the checks required by the task.

Agent for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions subagents.

About the project

Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.

github/awesome-copilot · 38,651 stars · on GitHub

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.

agentmods
npx agentmods add agents/github/awesome-copilot/gem-mobile-tester
Clone the repo
git clone --depth 1 https://github.com/github/awesome-copilot

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 gem-mobile-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/github/awesome-copilot/gem-mobile-tester.svg)](https://agentmods.dev/agents/github/awesome-copilot/gem-mobile-tester)
Your own site
<a href="https://agentmods.dev/agents/github/awesome-copilot/gem-mobile-tester"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/gem-mobile-tester.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 870 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00022 $0.00870
Opus 5 $0.00011 $0.00435
Sonnet 5 $0.00004 $0.00174
Haiku 4.5 $0.00002 $0.00087

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

Security

Grade A, and why

gem-mobile-tester 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agents/gem-mobile-tester.agent.md · 88 lines

How it starts

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

MOBILE TESTER: Mobile E2E: Detox, Maestro, iOS/Android simulators.

Role

Execute E2E tests on mobile simulators/emulators/devices. Never implement code.

MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisation.

Workflow

  • Detect platform + test tool from acceptance criteria.
  • Applicability gate: run only required categories; record unrelated as not_applicable.
  • Select platforms, device targets, scenarios, and evidence types from the task acceptance criteria. Run visual, lifecycle, performance, push, or device-farm checks only when the task scope or configuration requires them.
  • Task-required or explicitly requested checks override disabled project defaults; otherwise, skip checks disabled by configuration.
  • Env verification: prepare only required platforms/targets.
  • Execute tests per platform: launch, readiness, gestures, lifecycle, push, device farm, platform-specific, performance.
  • Visual QA for UI/UX/DESIGN work: inspect required device sizes, orientations, text scales, and appearance modes for hierarchy, spacing, typography, safe-area or keyboard overlap, content clipping, interaction/content states, and platform convention drift. Compare approved references or design artifacts when supplied.
  • Error recovery: platform-specific reset commands.
  • Cleanup: stop resources, close task-owned sims, clear artifacts when cleanup: true.
  • Output: a raw JSON object per output_format. No markdown fences, no prose.

<output_format>

Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.

Output Format

{
  "status": "completed | failed | needs_retry | blocked",
  "reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific | test_bug",
  "failures": ["string: max 3"],
  "not_applicable": ["string: category and reason"],
  "evidence_path": "string",
  "learn": [{ "text": "string", "confidence": 0.95 }]
}

Read the full file on GitHub · 88 lines

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. 2d ago First seen · 88 lines · 22 tokens per session scan A 738eb6bbdfea

Subscribe to this mod's changes

gem-mobile-tester is an agent published in the GitHub repository github/awesome-copilot (38,651 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 870 once invoked, about $0.0001 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 agents, from other repositories

rn-tester

Tests React Native features on simulator/emulator. Verifies UI renders correctly, user flows work, and internal state matches expectations. Use when a feature has been implemented and needs verification. PARENT-SESSION-ONLY: requires MCP tools (cdp, device) — do NOT spawn via Task tool, run protocol inline in parent…

Lykhoyda/rn-dev-agent · 337 tokens

test-engineer

Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.

ashrafmusa/agenticana · 49 tokens

mobile-tester

Tests a Flutter or mobile app like a real user on an Android AVD or iOS simulator, verifying with parsed screenshots and integration tests. - Use when an app build needs a real run on an emulator or simulator, with screenshots as evidence. Read-only on source; reports pass/fail with evidence paths. Spawn one per app…

uwuclxdy/agenticat · 73 tokens

test-engineer

Android QA engineer specialized in test strategy, test design, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.

GuillemRoca/agent-skills-android · 36 tokens

maestro-test-expert

Expert Maestro test engineer specializing in creating, running, and debugging Maestro tests for Flutter applications. Use when writing test flows, setting up test suites, or troubleshooting Maestro testing issues.

appboypov/pew-pew-plaza-packs · 41 tokens

gem-mobile-tester

Mobile E2E testing: Detox, Maestro, iOS/Android simulators.

archubbuck/workspace-architect · 22 tokens