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 yutori-ai/yutori-mcp --skill 07-iphone-mirroringgit clone --depth 1 https://github.com/yutori-ai/yutori-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/yutori-ai/yutori-mcp/07-iphone-mirroring)<a href="https://agentmods.dev/skills/yutori-ai/yutori-mcp/07-iphone-mirroring"><img src="https://agentmods.dev/badge/skills/yutori-ai/yutori-mcp/07-iphone-mirroring/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/yutori-ai/yutori-mcp/07-iphone-mirroring"><img src="https://agentmods.dev/badge/skills/yutori-ai/yutori-mcp/07-iphone-mirroring.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.00052 | $0.01124 |
| Opus 5.5 | $0.00021 | $0.00450 |
| Sonnet 5.5 | $0.00010 | $0.00225 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
yutori-iphone-mirroring 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 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.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iPhone Mirroring (Experimental)
This capability is purely experimental. Reliability is not guaranteed, and background typing, scrolling, app switching, and reconnection may fail. Do not present it as a supported production workflow.
Control an iPhone through Apple's iPhone Mirroring window on the Mac. The iPhone UI is a visual surface inside the Mac app: expect pixel actions rather than semantic accessibility elements.
Requirements
- Yutori computer use is ready (
uvx yutori-mcp computer-use doctor). - iPhone Mirroring is already paired and authorized.
- The Mac and iPhone meet Apple's Continuity requirements; keep the iPhone nearby and locked. Unlocking or using the iPhone directly ends mirroring.
- The user understands that content visible in the mirrored iPhone window is sent to Yutori for the run. Ask them to close or remove sensitive widgets before a benchmark.
If setup or authentication is required, stop and ask the user to complete it. Never request their Mac/iPhone password, passcode, passkey, biometric approval, or verification code.
Run an iPhone task
Always use window-scoped background capture so the agent sees and drives only iPhone Mirroring. Never enable foreground fallback for this skill: if an action cannot be delivered in the background, stop and report the blocked action instead of taking over the Mac desktop.
{
"task": "You are controlling an iPhone inside Apple iPhone Mirroring. Treat clicks as taps and scrolling or dragging as iPhone swipes. Use Command-3 to open iPhone Spotlight, type an exact app name, and press Return instead of searching across Home screens. Command-1 opens iPhone Home and Command-2 opens the iPhone App Switcher. Do not use the macOS Dock, menus, other apps, or shell commands. Take a fresh screenshot after each visual change. TASK: $ARGUMENTS",
"app": "iPhone Mirroring",
"mode": "background",
"allow_local_shell": false,
"minutes": 10,
"max_steps": 100
}
Tell the user they may keep using other Mac apps, but must leave iPhone Mirroring and the iPhone alone.
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 · 101 lines · 52 tokens per session scan A 381df4fe44a2
yutori-iphone-mirroring is a skill published in the GitHub repository yutori-ai/yutori-mcp (25 stars, last pushed 25d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,124 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-10.
Other skills, from other repositories
rn-device-control
This skill should be used when the user asks to "control the simulator", "take a screenshot", "boot the emulator", "install the app", "read UI hierarchy", "manage device state", "open a deep link", "grant permissions", "stream native logs", "disable animations", "change device locale", or needs guidance on xcrun…
rn-feature-development
This skill should be used when building any new feature in a React Native or Expo app, or when the $rn-dev-agent:rn-feature-dev command runs. Triggers on "build a feature", "add X to the app", "implement Y", "create a new screen", "rn-feature-dev", "feature development", "build me X", "add a screen", "wire up this…
using-rn-dev-agent
Entry point for the rn-dev-agent plugin. Maps user intent to the right command, agent, or skill. Use at the START of any React Native development conversation. Triggers on "I want to build", "build a feature", "add a feature to the app", "test this", "something is broken", "fix the crash", "help with my React Native…
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
rn-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — read project instructions and the declared package manager, inventory sessions/Metro/devices read-only, establish one exclusive simulator/emulator via typed session actions, apply and verify package integration and…
capturing-proof
This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…