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 clivejefferies/mobile-debug-tools --skill mobile-debug-tools-usagegit clone --depth 1 https://github.com/clivejefferies/mobile-debug-toolsWrote 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/clivejefferies/mobile-debug-tools/mobile-debug-tools-usage)<a href="https://agentmods.dev/skills/clivejefferies/mobile-debug-tools/mobile-debug-tools-usage"><img src="https://agentmods.dev/badge/skills/clivejefferies/mobile-debug-tools/mobile-debug-tools-usage/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/clivejefferies/mobile-debug-tools/mobile-debug-tools-usage"><img src="https://agentmods.dev/badge/skills/clivejefferies/mobile-debug-tools/mobile-debug-tools-usage.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.00039 | $0.00837 |
| Opus 5.5 | $0.00016 | $0.00335 |
| Sonnet 5 | $0.00008 | $0.00167 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
mobile-debug-mcp 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 yesterday.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile-debug MCP verification
Use mobile-debug MCP to make a product claim observable on a real device or emulator. A successful tap proves only that the input was delivered; verify the resulting UI, notification, or persisted state before reporting success.
Choose the lightest evidence that proves the claim
- Use an accessibility assertion such as
expect_element_visibleorwait_for_uifor an accessible label, enabled state, or changed control. - Use a screenshot when visual layout, system UI, or notification content matters.
- Use a debug snapshot only when the screen does not explain a failed action or an accessibility-tree assertion is needed.
- Use Android shell commands only for device navigation or system surfaces that MCP cannot expose. Do not treat shell output as proof of user-visible behaviour.
Avoid repeated screenshots and snapshots when a targeted accessibility assertion is enough.
Keep interaction fast
Treat each MCP call as a round trip and use the fastest path that still proves the behaviour. Prefer the following sequence:
- Wait for one stable, uniquely identifiable control.
- Tap its returned element id.
- Wait for the specific resulting state.
Do not wait before every tap when the current screen and element id are already known. Do not poll unchanged screens. Use short timeouts for ordinary controls; reserve longer waits for known asynchronous work such as model initialisation or network calls.
Use compact responses for routine actions. If action dispatch is reliable but
verification is slow or unavailable, dispatch with verification disabled and
verify at meaningful checkpoints with one focused accessibility assertion or
screenshot. Do not assume light verification is faster: use it only when it
has returned useful results reliably on the current MCP version and device.
Prefer a stable element selector when the accessibility tree exposes one. Use coordinates only when needed, and take a fresh screenshot immediately before a coordinate tap on system UI, notifications, or any screen where layout may have changed. Never reuse coordinates after expanding/collapsing a notification, changing orientation, or switching screens.
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.
- yesterday First seen · 75 lines · 39 tokens per session scan A b3347226e741
mobile-debug-mcp is a skill published in the GitHub repository clivejefferies/mobile-debug-tools (11 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 837 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-09-28.
Other skills, from other repositories
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.
argent-create-flow
Create, record, edit, replay, or repair reusable Argent flow YAML files. Use when the user asks to record or replay a repeatable device path, set up profiling or an A/B comparison, or invoke the authoring engine behind argent-qa-flows. Also use before repeating three or more interactions. For one-off UI checks…
mobilewright-cli
Automate iOS and Android apps on simulators, emulators and real devices, explore screens and write Mobilewright tests.
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.
Detox Mobile Testing
Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.