CC Pocket is a mobile and desktop client for controlling Codex and Claude coding-agent sessions through a self-hosted Bridge Server running on another computer. It lets users start sessions, approve actions, answer questions, review changes, and continue coding from supported devices. The catalogue entries provide the skills, hooks, MCP servers, agents, instructions, and settings used by this client.
Borrowing it
Nothing to install: this file belongs to K9i-0/ccpocket. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/K9i-0/ccpocket/main/.claude/skills/mobile-automation/SKILL.mdgit clone --depth 1 https://github.com/K9i-0/ccpocketWrote 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/k9i-0/ccpocket/mobile-automation)<a href="https://agentmods.dev/skills/k9i-0/ccpocket/mobile-automation"><img src="https://agentmods.dev/badge/skills/k9i-0/ccpocket/mobile-automation/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/k9i-0/ccpocket/mobile-automation"><img src="https://agentmods.dev/badge/skills/k9i-0/ccpocket/mobile-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00510 |
| Opus 5.5 | $0.00015 | $0.00204 |
| Sonnet 5.5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
mobile-automation 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.
What it actually says
Mobile Automation
検証対象に応じて必要な参照だけ読む。dart-mcp / Marionette で実行時の状態を確認する。
- 起動・接続・CLIとMCPの使い分け: references/startup.md
- Bridge不要のMock UI検証と要素キー: references/mock-and-keys.md
- 実際のBridge通信を含む検証: references/e2e.md
- 接続・ジェスチャー・モック制限の問題: references/troubleshooting.md
実行範囲
- 既定はiOSシミュレーターとテスト用Bridge
8766。ユーザーが指定したデバイス・接続先を優先する。本番8765のプロセスを停止しない。 - プロジェクトルートは
git rev-parse --show-toplevel、アプリはその配下のapps/mobile。 - 検証する挙動と期待結果を決め、関連するシナリオを選ぶ。単純なUI確認は直接操作する。複数画面の独立した検証は、利用可能なら
e2e-verifier等へ委譲できる。 - 操作には現在の
get_interactive_elementsのキー・boundsを使う。画面遷移やジェスチャー後は結果を確認する。 - 要素・ログで挙動を確認し、外観・レイアウトの変更はスクリーンショットで目視する。枚数は検証対象に応じて選ぶ。
- 終了時は自分が起動したアプリ・BridgeだけPIDを指定して停止する。プレビュー継続を依頼されている場合は残し、接続方法を報告する。
- 検証結果と未確認の範囲を報告する。Mock表示の成功を実通信の成功として扱わない。
What ships with it
4 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.
- 1mo ago Changed · -310 lines · -101 tokens per session 44dc29614b93
- 1mo ago First seen · 334 lines · 138 tokens per session scan A 10ec0283a16a
mobile-automation is a skill published in the GitHub repository K9i-0/ccpocket (1,093 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 510 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
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.
mobiloop-mobile-qa
Test mobile apps with MobiLoop MCP, collect device evidence, and fix and retest confirmed failures within the user's scope. Use for Flutter, React Native, Android, or iOS QA on an emulator, simulator, or device, including relevant mobile security checks.
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.
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.
ios-e2e-readiness
Use when iOS mobile E2E flows are flaky, SwiftUI and UIKit surfaces disagree with automation, mixed screens are ambiguous, retries hide the real issue, or the team keeps collapsing the problem to timing-only or SwiftUI-only without checking iOS-specific readiness contracts.
mobile-e2e-readiness-baseline
Use when mobile E2E flows are flaky across Android and iOS, visible screens are not reliably actionable, retries hide the real problem, or a team needs a platform-neutral readiness review before platform-specific guidance.