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 agentmods add agents/archubbuck/workspace-architect/gem-mobile-testergit clone --depth 1 https://github.com/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/gem-mobile-tester)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/gem-mobile-tester"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/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.00870 |
| Opus 5 | $0.00011 | $0.00435 |
| Sonnet 5 | $0.00004 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
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.
This is a copy
100% identical to gem-mobile-tester — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 }]
}
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.
- 2d ago First seen · 88 lines · 22 tokens per session scan A 738eb6bbdfea
gem-mobile-tester is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 2d ago), licensed ISC. 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. It is 100% identical to gem-mobile-tester, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
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.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
code-reviewer
Senior Android code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, performance. Use for thorough code review before merge.
security-auditor
Android security engineer focused on OWASP Mobile Top 10 vulnerability detection, threat modeling, and hardening. Use for security review before release or threat analysis on a change.
platform-adapter
Doc-driven platform integration agent. Converts web apps to LINE MINI App (LIFF SDK), PWA (Next.js), and Capacitor (iOS/Android); Expo & Tauri are secondary/legacy. Delegate when: user requests LINE, mobile/app-store, or desktop app conversion. Always pulls current official docs before writing platform code — no…
al-presales
Technical PreSales Agent for AL/Business Central projects. Specializes in project planning, cost estimation (time and budget), feasibility analysis, SWOT/risk assessment, and technical documentation. Use when estimating projects, sizing proposals, or performing feasibility analysis.