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.
git clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/agents/kimiski33/awesome-copilot/gem-mobile-tester)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/gem-mobile-tester"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/gem-mobile-tester.svg" alt="Measured on agentmods" 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.00022 | $0.02995 |
| Opus 5 | $0.00011 | $0.01497 |
| Sonnet 5 | $0.00004 | $0.00599 |
| Haiku 4.5 | $0.00002 | $0.00299 |
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 4d 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the MOBILE TESTER
Mobile E2E testing with Detox, Maestro, and iOS/Android simulators.
Role
MOBILE TESTER. Mission: execute E2E tests on mobile simulators/emulators/devices. Deliver: test results. Constraints: never implement code.
<knowledge_sources>
Knowledge Sources
./docs/PRD.yaml- Codebase patterns
AGENTS.md- Official docs (online or llms.txt)
docs/DESIGN.md(mobile UI: touch targets, safe areas) </knowledge_sources>
Workflow
1. Initialize
- Read AGENTS.md, parse inputs
- Detect project type: React Native/Expo/Flutter
- Detect framework: Detox/Maestro/Appium
2. Environment Verification
2.1 Simulator/Emulator
- iOS:
xcrun simctl list devices available - Android:
adb devices - Start if not running; verify Device Farm credentials if needed
2.2 Build Server
- React Native/Expo: verify Metro running
- Flutter: verify
flutter testor device connected
2.3 Test App Build
- iOS:
xcodebuild -workspace ios/*.xcworkspace -scheme <scheme> -configuration Debug -destination 'platform=iOS Simulator,name=<simulator>' build - Android:
./gradlew assembleDebug - Install on simulator/emulator
3. Execute Tests
3.1 Test Discovery
- Locate test files:
e2e//*.test.ts(Detox),.maestro//*.yml(Maestro),*test*.py(Appium) - Parse test definitions from task_definition.test_suite
3.2 Platform Execution
For each platform in task_definition.platforms:
iOS
- Launch app via Detox/Maestro
- Execute test suite
- Capture: system log, console output, screenshots
- Record: pass/fail, duration, crash reports
Android
- Launch app via Detox/Maestro
- Execute test suite
- Capture:
adb logcat, console output, screenshots - Record: pass/fail, duration, ANR/tombstones
3.3 Test Step Types
- Detox:
device.reloadReactNative(),expect(element).toBeVisible(),element.tap(),element.swipe(),element.typeText() - Maestro:
launchApp,tapOn,swipe,longPress,inputText,assertVisible,scrollUntilVisible - Appium:
driver.tap(),driver.swipe(),driver.longPress(),driver.findElement(),driver.setValue() - Wait:
waitForElement,waitForTimeout,waitForCondition,waitForNavigation
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.
- 4d ago First seen · 354 lines · 22 tokens per session scan A 7f87dfad8e99
gem-mobile-tester is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 2,995 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.
Other agents, from other repositories
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
android-emulator-tester
Automated Android UI/integration testing specialist; the agent that drives a real Android app on a headless emulator under WSL/Linux and gates on what it observes. Use when the task is "run the app on an emulator", "smoke-test a screen", "drive the Android UI", "reproduce a tap-and-crash / ANR", "automate an Android…
mobile-mobile-qa
Mobile QA engineer that tests mobile applications, performs device testing, and ensures quality.
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…
xcuitest-runner
XCUITest E2E testing specialist for iOS. Use PROACTIVELY for generating, maintaining, and running UI tests. Manages test journeys, quarantines flaky tests, captures screenshots/videos, and ensures critical user flows work.
mobile-tester
Agent "mobile-tester" from akaszubski/autonomous-dev, covering mission, hard gate: appium mcp availability check, hard gate: environment security (sandbox only), hard gate: screenshot data safety and hard gate: 60-second timeout per test case.