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 agentmods add skills/jaycrl/mobilevc/mobilevc-installernpx skills add JayCRL/MobileVC --skill mobilevc-installergit clone --depth 1 https://github.com/JayCRL/MobileVCWrote 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/jaycrl/mobilevc/mobilevc-installer)<a href="https://agentmods.dev/skills/jaycrl/mobilevc/mobilevc-installer"><img src="https://agentmods.dev/badge/skills/jaycrl/mobilevc/mobilevc-installer.svg" alt="Measured on agentmods" 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.00222 | $0.01238 |
| Opus 5 | $0.00111 | $0.00619 |
| Sonnet 5 | $0.00044 | $0.00248 |
| Haiku 4.5 | $0.00022 | $0.00124 |
Grade A, and why
mobilevc-installer 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 6d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mobilevc-installer
Install and run MobileVC for the user. The user's dev machine becomes the Claude Code backend; the phone runs the official client app and connects to it over LAN or through the public Relay flow.
GitHub: https://github.com/JayCRL/MobileVC npm: https://www.npmjs.com/package/@justprove/mobilevc
What you do
Run these steps in order. Stop and report to the user as soon as anything fails.
Step 1 — Preflight
Before installing, check the environment. Run these commands and confirm:
node --version # require >= 18.0.0
npm --version
If node is missing or older than 18, STOP and tell the user how to install Node.js (brew install node, nvm install 20, or https://nodejs.org). Do NOT proceed.
Step 2 — Install the npm package
Try the global install first:
npm install -g @justprove/mobilevc
If it fails with EACCES or permission errors, do NOT use sudo. Instead suggest one of:
npm config set prefix ~/.npm-global && export PATH=~/.npm-global/bin:$PATHthen re-run installnvm use <version>if the user has nvmnpm install --prefix ~/.local @justprove/mobilevcand add~/.local/binto PATH
Verify:
mobilevc --help
Step 3 — First-run setup (interactive)
Tell the user that mobilevc start will ask three questions on first run:
- Language —
zhoren - Port — default
8001. Pick something else if 8001 is busy. - Auth token — any string the user wants. The phone client will need this to connect.
If the user has not picked a token yet, suggest something memorable but non-trivial (e.g. mvc- plus 8 random chars).
Important: token input is hidden in the terminal. Tell the user to type the token normally and press Enter even though no characters are shown.
Step 4 — Start the backend
mobilevc start
This will:
- Run
mobilevc setupif no config exists yet - Spawn the prebuilt server binary in the background (logs in
~/.mobilevc/logs/) - Print a LAN QR code in the terminal that encodes
<host>:<port>+ auth token
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.
- 6d ago First seen · 123 lines · 222 tokens per session scan A ccfbe88fd5b3
mobilevc-installer is a skill published in the GitHub repository JayCRL/MobileVC (210 stars, last pushed 2mo ago), licensed MIT. It adds 222 tokens to every session and 1,238 once invoked, about $0.0011 per session on Opus 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
at_client_skills-sdk
Use this skill when a developer is building a Dart or Flutter app that depends on atclient or atclientflutter from pub.dev, stores or shares data via the Atsign Protocol, needs onboarding (CRAM new-atsign, atKeys file, keychain, APKAM) or APKAM enrollment, or asks about AtCollection , CItem , Query , sub-collections…
mobile-automation
MCP (dart-mcp + Marionette) を使ったFlutterアプリのE2E自動化・UI検証ガイド。シミュレーターでのUI動作確認、モックプレビュー検証、Bridge経由のE2Eテスト、スクリーンショット撮影など、アプリの動作検証が必要なときに使う。「動作確認して」「UIを検証して」「E2Eテスト」「シミュレーターで確認」「モックで確認」と言われたときや、UI変更後の検証フェーズで使用すること。.
update-store
ストア情報の更新自動化 — スクリーンショット撮影（シミュレーター × モック画面 × Marionette MCP）とメタデータテキスト更新。ストア更新、スクショ更新、App Store / Google Play のメタデータ更新、リリースノート作成の際に使用すること。.
submit-store-review
App Store Connect・Google Playの現在の公開版をAPIで調べ、既存の最新安定ビルドとの差分から4言語のリリースノートを作成し、CLI/APIで審査へ提出・再提出する。新しいビルドを作るrelease-appとは分離し、「最新を審査提出して」「ストア審査へ提出して」「App Reviewに出して」「Google Playの審査を進めて」「却下対応して再提出して」と依頼されたときに使用する。.
release-app
アプリのリリース（バージョンbump + CHANGELOG + タグ → GH Actions で自動ビルド・配布）。iOS / Android / macOS / Linux / Windows の任意の組み合わせでリリースできる。「リリース」「バージョン上げて」「リリースして」と言われたときに使う。.
flutter-upgrade
Flutter SDKバージョンアップグレード対応。新バージョンのリリースノート・Breaking Changes調査、コードベース影響分析、mise/CI/Shorebird含むプロジェクト全体の対応タスクリスト作成と実行。「Flutterアップグレード」「Flutter X.Y.Zがリリースされた」「Flutter最新化」「Flutter更新」と言われたとき、またはFlutterの新バージョンについて言及されたときに使用する。.