Borrowing it
Nothing to install: this file belongs to band-app/band. 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/band-app/band/main/.claude/skills/mobile-verify/SKILL.mdgit clone --depth 1 https://github.com/band-app/bandWrote 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/band-app/band/mobile-verify)<a href="https://agentmods.dev/skills/band-app/band/mobile-verify"><img src="https://agentmods.dev/badge/skills/band-app/band/mobile-verify/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/band-app/band/mobile-verify"><img src="https://agentmods.dev/badge/skills/band-app/band/mobile-verify.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.00129 | $0.05148 |
| Opus 5.5 | $0.00052 | $0.02059 |
| Sonnet 5.5 | $0.00026 | $0.01030 |
| Haiku 4.5 | $0.00013 | $0.00515 |
Grade C, and why
mobile-verify scanned grade C with 1 finding 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 today.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/band-ios-sim.lock How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mobile-verify
Runs the mobile app's acceptance flows on the iOS simulator against a real Band hub, from a
worktree, without touching the real ~/.band, the user's running hub or the desktop app.
Everything below runs from the worktree root unless a step says otherwise.
One-time setup on a Mac
Check each tool first and install only what is missing. All of it is user space (Homebrew).
- Xcode with an iOS simulator runtime:
xcodebuild -versionandxcrun simctl list devices available | grep iPhonemust both print something. Installing Xcode is a manual step; stop and tell the user if it is missing. - CocoaPods:
pod --version, elsebrew install cocoapods. - Java 17 for Maestro:
/opt/homebrew/opt/openjdk@17/bin/java -version, elsebrew install openjdk@17. The verify script puts it on PATH itself, so no shell profile change is needed. - Maestro:
PATH="/opt/homebrew/opt/openjdk@17/bin:$PATH" maestro --version(the script also looks in~/.maestro/bin), elsebrew tap mobile-dev-inc/tap && brew install mobile-dev-inc/tap/maestro. Without Java 17 on PATH, a baremaestro --versionfails with "Unable to locate a Java Runtime" even when Maestro is installed. - Node 24 (
.nvmrc):node --versionmust print v24. If it doesn't, put a Node 24 first on PATH for every command below (for example~/.nvm/versions/node/v24.*/bin). - The workspace installed:
pnpm install. On a fresh worktree this is the longest step (about 15 minutes with a cold pnpm store). - Disk: a build needs about 2.5 GB in the worktree (
apps/mobile/buildabout 1.9 GB, the generatedapps/mobile/iosabout 650 MB). Checkdf -h .first.
Every run
-
Build the hub bundle once per worktree (the throwaway hub runs it):
pnpm build:webSkip this when
apps/hub/dist/start-server.mjsalready exists and the change touches onlyapps/mobile. -
Run the flows:
node apps/mobile/scripts/verify.mjs
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.
- today Changed · +1 lines 114c58e1059e
- 9d ago Changed · +2 lines 94d9fbd716f8
- 11d ago Changed · +7 lines be31d4ec3f8b
- 12d ago Changed · +25 lines scan A → C ff17c5f53577
- 13d ago Changed · +6 lines 175648967b16
- 14d ago First seen · 171 lines · 129 tokens per session scan A 28cffe24a27d
mobile-verify is a skill published in the GitHub repository band-app/band (5 stars, last pushed today), licensed MIT. It adds 129 tokens to every session and 5,148 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-15.
Other skills, from other repositories
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
eas-simulator
Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…