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 enessubass/mobiloop-mcp --skill mobiloop-mobile-qagit clone --depth 1 https://github.com/enessubass/mobiloop-mcpWrote 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/enessubass/mobiloop-mcp/mobiloop-mobile-qa)<a href="https://agentmods.dev/skills/enessubass/mobiloop-mcp/mobiloop-mobile-qa"><img src="https://agentmods.dev/badge/skills/enessubass/mobiloop-mcp/mobiloop-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/skills/enessubass/mobiloop-mcp/mobiloop-mobile-qa"><img src="https://agentmods.dev/badge/skills/enessubass/mobiloop-mcp/mobiloop-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.00060 | $0.01787 |
| Opus 5.5 | $0.00024 | $0.00715 |
| Sonnet 5.5 | $0.00012 | $0.00357 |
| Haiku 4.5 | $0.00006 | $0.00179 |
Grade A, and why
mobiloop-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 today.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MobiLoop Mobile QA
Turn the user's mobile testing request into executed scenarios with observable assertions, evidence, and bounded fixes. The agent chooses scenarios and patches; MobiLoop runs guarded tools. Work within the requested app, device, environment, and authorization.
Requires a local MobiLoop MCP connection or installed mobiloop CLI, the target platform SDK, and Appium with its platform driver for UI tests. iOS simulator tests require macOS and Xcode.
Establish The Run
- Discover the connected MobiLoop tools and their input schemas. Names below are server tool names; use the client's actual namespace. Read
policy.list_toolsfor effective approval requirements. If only the installed CLI is available, usemobiloop list-tools --jsonandmobiloop call <tool.name> '<json-args>'. If neither interface exists, report the missing MobiLoop connection. - Establish the mobile workspace, target platform and device, test goal, available test account/data, and permission to modify code or app state from the user's request. Reuse authorization already given for the same scope. Testing permission does not imply permission to erase app data, use production accounts, publish, or deploy. A request to analyze or generate scenarios alone stops before device actions and code changes.
- Run
build.detect_projectandenv.preflightfor the target platform; also check the framework when needed. Usedevice.list_devicesorios.list_simulatorsto select the intended target. Check Appium readiness before UI work. Configure its endpoint on the host; do not supplyserverUrloverrides in secure mode. Resolve missing SDKs, drivers, or services only when setup is authorized; otherwise report the prerequisite. - Establish the run's limits before execution. Honor lower user/host limits. When unspecified, use at most three fix attempts, five test iterations, and 30 minutes total. Count scenario executions and orchestrator retries toward the test limit, patches toward the fix limit, and all tool execution time toward the runtime limit. Do not restart counters for each scenario. Use a fresh host-configured run ID when available and retain returned artifact paths rather than guessing filenames.
What ships with it
2 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.
- today First seen · 65 lines · 60 tokens per session scan A 08fce91fb47c
mobiloop-mobile-qa is a skill published in the GitHub repository enessubass/mobiloop-mcp (11 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 1,787 once invoked, about $0.0002 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-10-16.
Other skills, from other repositories
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.
noqa-testing
Use this skill when the user wants to boot and interact with iOS or Android devices/simulators — inspect the screen, execute actions, generate or edit test cases, or run UI tests via the noqa platform.
zmr-mobile-testing
Use when testing mobile apps with Zeno Mobile Runner, integrating app-local .zmr setup, driving Android or iOS simulator scenarios, using JSON-RPC or MCP agent sessions, exporting traces, or comparing mobile runner benchmarks.
aco
Drive a live Appium session from the shell with the aco CLI. Use when the user wants to interact with a running mobile app on an iOS simulator, Android emulator, or connected real device — tap, swipe, type, screenshot, read the screen/page source, find UI elements, switch to a WebView context, or call iOS/Android…
mobile-tester
You are the Mobile Tester Specialist. You connect to real Android/iOS devices and write, execute, and report on mobile UI test cases. You master THREE testing modalities.
android-e2e-readiness
Use when Android mobile E2E flows are flaky, Compose and View screens disagree with automation, hybrid screens are ambiguous, retries hide the real issue, or the team keeps collapsing the problem to selector-vs-timing without checking Android-specific readiness contracts.