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 biggora/claude-plugins-registry --skill test-mobile-appgit clone --depth 1 https://github.com/biggora/claude-plugins-registryWrote 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/biggora/claude-plugins-registry/test-mobile-app)<a href="https://agentmods.dev/skills/biggora/claude-plugins-registry/test-mobile-app"><img src="https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/test-mobile-app.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.00181 | $0.02466 |
| Opus 5 | $0.00090 | $0.01233 |
| Sonnet 5 | $0.00036 | $0.00493 |
| Haiku 4.5 | $0.00018 | $0.00247 |
Grade A, and why
test-mobile-app scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] API endpoints respond to direct `curl http://<host-ip>:<port>/health` from terminal before running app tests How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile App Testing Skill
This skill enables Claude to perform end-to-end mobile application testing:
- Analyze the app structure and infer user-facing functionality
- Generate use cases from an end-user perspective
- Write concrete test scenarios with expected results
- Execute tests via Appium + Android emulator (or interpret results statically)
- Produce a structured HTML/Markdown test report
Phase 1 — App Analysis
What to collect
Before generating use cases, gather as much context as possible:
- Source code (Android/Java/Kotlin, iOS/Swift, React Native, Flutter)
- APK file — use
androguardto extract Activity list, permissions, Manifest - Screenshots — analyze UI from images
- Description — what the app does, target audience
APK Analysis (Android)
Read scripts/analyze_apk.py for full script. Quick usage:
python3 scripts/analyze_apk.py path/to/app.apk
Outputs: package name, activities, permissions, strings → feeds into use case generation.
Source Code Analysis
If source is available, scan for:
- Screen/Activity/Fragment/Page names → each is a potential use case surface
- Navigation graphs (React Navigation, NavController)
- API endpoints called (network requests)
- Form fields, validation logic
- Authentication flows
Phase 2 — Use Case Generation
Methodology
Think from the perspective of a real end user — not a developer. Ask: "What would a person actually do with this app?"
Use case format:
UC-<N>: <Short Title>
Actor: End User
Precondition: <What must be true before this action>
Steps:
1. <action>
2. <action>
...
Expected outcome: <what the user sees/gets>
Priority: High / Medium / Low
Use Case Categories to Always Cover
- Onboarding — first launch, tutorial, permissions prompt
- Authentication — registration, login, logout, password reset
- Core Feature Flow — the primary value action of the app (1-3 flows)
- Data Entry — any form: required fields, validation, error states
- Navigation — bottom nav, back button, deep links
- Empty States — what happens when there's no data
- Error Handling — no internet, server error, invalid input
- Settings / Profile — change preferences, update data
- Notifications — if the app uses push notifications
- Accessibility — basic: is text readable, are tap targets big enough
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 288 lines · 181 tokens per session scan A 156f8553965e
test-mobile-app is a skill published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 9d ago), licensed MIT. It adds 181 tokens to every session and 2,466 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.