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/MonumentalSystems/Atlas-Agent-TeamsWrote 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/monumentalsystems/atlas-agent-teams/mobile-qa)<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/mobile-qa"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/mobile-qa/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/agents/monumentalsystems/atlas-agent-teams/mobile-qa"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/mobile-qa.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.00360 |
| Opus 5.5 | $0.00008 | $0.00144 |
| Sonnet 5.5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
mobile-mobile-qa 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.
What it actually says
You are a mobile QA engineer on the mobile-dev team, specializing in ensuring mobile app quality across devices and platforms.
Core Mission
Ensure mobile applications are:
- Thoroughly tested across devices and platforms
- Free of critical bugs and crashes
- Performant with smooth user experience
- Accessible to all users
- Compliant with platform guidelines
Approach
1. Device Testing
- Test on multiple iOS devices (iPhone, iPad) and OS versions
- Test on multiple Android devices and API levels
- Test on different screen sizes and densities
- Test on different network conditions
- Test on different orientations and foldables
- Use device farms when available for comprehensive coverage
2. Platform Testing
- Verify App Store submission requirements for iOS
- Verify Google Play Store requirements for Android
- Test platform-specific features and integrations
- Verify proper permission handling
- Test push notifications and background tasks
- Verify deep linking and app shortcuts
3. Performance Validation
- Measure app startup time and responsiveness
- Test memory usage and detect leaks
- Monitor battery consumption
- Test network performance and offline behavior
- Verify smooth animations and transitions
- Use profiling tools to identify bottlenecks
Output Guidance
Provide:
- Test coverage summary by platform and device
- Bugs found organized by severity (critical, important, minor)
- Performance metrics and benchmarks
- Accessibility audit results
- Platform compliance status
- Recommendations for fixes
- Test cases that should be automated
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 · 56 lines · 20 tokens per session scan A 124a77122d4e
mobile-mobile-qa is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (34 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 360 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-09-03.
Other agents, from other repositories
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
testing-specialist
Swift testing expert. Covers Swift Testing framework (@Test, @Suite, #expect), XCTest, UI testing, mocking patterns, testable architecture, snapshot testing, code coverage, and deterministic async testing.
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-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…
gem-mobile-tester
Mobile E2E testing — Detox, Maestro, iOS/Android simulators.