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 skills add MonumentalSystems/Atlas-Agent-Teams --skill mobile-testinggit 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/skills/monumentalsystems/atlas-agent-teams/mobile-testing)<a href="https://agentmods.dev/skills/monumentalsystems/atlas-agent-teams/mobile-testing"><img src="https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/mobile-testing.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.00014 | $0.00513 |
| Opus 5 | $0.00007 | $0.00257 |
| Sonnet 5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00051 |
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 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Testing Guidelines
Mobile Testing Strategies
- Test on real devices when possible
- Use simulators and emulators for initial testing
- Test on multiple iOS and Android versions
- Test on different screen sizes and densities
- Test on different network conditions
- Implement automated testing for critical paths
- Use device farms for comprehensive coverage
Device Farm Testing
- Use Firebase Test Lab for Android
- Use AWS Device Farm for cross-platform testing
- Use BrowserStack for real device testing
- Test on popular device configurations
- Test on older devices for performance
- Test on different manufacturer devices (Android)
- Test on different iOS device models
Emulator and Simulator Testing
- Use iOS Simulator for iOS testing
- Use Android Emulator for Android testing
- Test on different API levels
- Test on different screen configurations
- Use emulator features for testing (GPS, camera, etc.)
- Test with different language and region settings
- Test with accessibility features enabled
UI Testing Frameworks
- iOS: XCUITest for UI automation
- Android: Espresso for UI testing
- Cross-Platform: Appium for cross-platform UI tests
- React Native: Detox for React Native testing
- Flutter: Flutter integration testing
- Write maintainable UI tests with page object pattern
- Test critical user flows end-to-end
Performance Testing for Mobile
- Measure app startup time
- Test memory usage and detect leaks
- Monitor battery consumption
- Test network performance and latency
- Test offline behavior and sync
- Use profiling tools (Instruments, Android Profiler)
- Set performance budgets and monitor
Mobile Accessibility Testing
- Test with VoiceOver (iOS) and TalkBack (Android)
- Test with Dynamic Type (iOS) and font scaling (Android)
- Test with screen magnification
- Verify color contrast ratios
- Test with switch control and other assistive technologies
- Follow WCAG and platform accessibility guidelines
- Test with reduced motion settings
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 · 70 lines · 14 tokens per session scan A 75bde3c9832e
mobile-testing is a skill published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 27d ago), licensed MIT. It adds 14 tokens to every session and 513 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 skills, from other repositories
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
eas-simulator
EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas…
flutter-add-integration-test
Configures Flutter Driver for app interaction and converts MCP actions into permanent integration tests. Use when adding integration testing to a project, exploring UI components via MCP, or automating user flows with the integrationtest package.