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 metahub-tech/agent-fleet --skill using-iosgit clone --depth 1 https://github.com/metahub-tech/agent-fleetWrote 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/metahub-tech/agent-fleet/using-ios)<a href="https://agentmods.dev/skills/metahub-tech/agent-fleet/using-ios"><img src="https://agentmods.dev/badge/skills/metahub-tech/agent-fleet/using-ios/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/metahub-tech/agent-fleet/using-ios"><img src="https://agentmods.dev/badge/skills/metahub-tech/agent-fleet/using-ios.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.00069 | $0.03033 |
| Opus 5.5 | $0.00028 | $0.01213 |
| Sonnet 5.5 | $0.00014 | $0.00607 |
| Haiku 4.5 | $0.00007 | $0.00303 |
Grade B, and why
using-ios scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -X POST --data-binary @bg.png \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST --data-binary @bg.png \ How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using ios-device
Drive one or more iOS/iPadOS devices via the ios-device MCP server (FastMCP, streamable-http on Tailscale, port 8769). The server runs on a macOS host (Xcode + WDA requirement), and reaches the device via WebDriverAgent over USB (pymobiledevice3 usbmux forward). 26 tools across 9 categories.
Mental model
[You / Agent] -- streamable-http --> [macOS host running ios-device MCP]:8769
|
pymobiledevice3 USB forward
|
WebDriverAgent on iOS device
You drive the SERVER. The server drives WDA. WDA drives the DEVICE. You don't touch the device directly. WDA must be running on the device before UI tools work (see docs/platforms/ios.md for Xcode build steps).
Critical patterns
Coordinates are points (WDA coordinate space)
get_screen_size returns the device's logical size in points (e.g. {width: 390, height: 844} for iPhone 14). take_screenshot returns a PNG at point resolution (1x), NOT at the device's physical pixel resolution. tap(x, y) uses the same point space. No scaling needed on your end — WDA already handles the logical-to-physical mapping.
get_screen_size # {"width": 390, "height": 844}
take_screenshot # PNG also at 390x844 points
tap(x=195, y=422) # center of screen
tap / swipe / long_press — same naming as android-device
iOS uses touchscreens exactly like Android. Use tap, swipe, long_press — not click.
Keyboard: type_text vs press_key
| What | Tool | Note |
|---|---|---|
| Type into a focused input | type_text("hello") |
Routes via WDA /wda/keys → UIKit. Supports Unicode. Some custom text fields may not receive it — fall back to tap + clipboard paste if needed. |
| Physical buttons | press_key(key="home") |
Supported: home, volume_up, volume_down, lock only. No adb-style KEYCODE mapping — iOS exposes only these four physical buttons via WDA. |
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 · 187 lines · 69 tokens per session scan B 952ba9fb85a8
using-ios is a skill published in the GitHub repository metahub-tech/agent-fleet (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 3,033 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, 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
app_remix
Create a new Rome app from an App Store source, already installed or identified by a pinned Store version. Copy installed code locally or download and extract a Store bundle without installing the source. Never edit or overwrite an existing source app.
building-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
use-dom
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
ii-app
Use this skill when you need to initialize or restart local web and mobile app projects through the bundled Rust ii-app CLI instead of calling MCP tools.
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).
extract-apk
A workflow for finding an Android app on a connected device, exporting its APK, and turning it into searchable decompiled source files. An APK is the installable package used by Android apps.