Borrowing it
Nothing to install: this file belongs to ahmed3elshaer/everything-claude-code-mobile. 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/ahmed3elshaer/everything-claude-code-mobile/main/.opencode/commands/mobile-verify.mdgit clone --depth 1 https://github.com/ahmed3elshaer/everything-claude-code-mobileWrote 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/commands/ahmed3elshaer/everything-claude-code-mobile/mobile-verify)<a href="https://agentmods.dev/commands/ahmed3elshaer/everything-claude-code-mobile/mobile-verify"><img src="https://agentmods.dev/badge/commands/ahmed3elshaer/everything-claude-code-mobile/mobile-verify.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.00023 | $0.01478 |
| Opus 5 | $0.00012 | $0.00739 |
| Sonnet 5 | $0.00005 | $0.00296 |
| Haiku 4.5 | $0.00002 | $0.00148 |
Grade A, and why
mobile-verify 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 7d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Verify Command
Automated test verification with pass@k metrics for mobile development.
Usage
/mobile-verify # Run all tests with k=3
/mobile-verify --k=5 # Run tests 5 times
/mobile-verify --unit # Unit tests only
/mobile-verify --ui # UI/Espresso tests only
/mobile-verify --compose # Compose tests only
/mobile-verify --module=feature:auth# Specific module
/mobile-verify --class=AuthViewModelTest# Specific test class
/mobile-verify --flaky # Focus on flaky test detection
Pass@k Metrics
Pass@k measures reliability: how often tests pass when run k times.
| Pass@3 Score | Meaning | Action |
|---|---|---|
| 3/3 (100%) | Stable | No action needed |
| 2/3 (67%) | Somewhat flaky | Monitor |
| 1/3 (33%) | Flaky | Investigate |
| 0/3 (0%) | Failing | Fix required |
Verification Types
Unit Tests (JUnit)
/mobile-verify --unit --k=3
Runs JUnit tests k times:
- Executes
./gradlew testk iterations - Tracks pass/fail per iteration
- Identifies flaky tests
Output:
Unit Test Verification (k=3)
═════════════════════════════════
AuthViewModelTest:
testLogin() ✓✓✓ (3/3) 100%
testLogout() ✓✓✗ (2/3) 67% FLAKY
testTokenRefresh() ✓✓✓ (3/3) 100%
Overall: 8/9 (89%)
Flaky tests: 1
UI Tests (Espresso)
/mobile-verify --ui --k=3
Runs Espresso tests k times:
- Executes
./gradlew connectedAndroidTest - Handles device/emulator setup
- Measures test stability
Compose Tests
/mobile-verify --compose --k=3
Runs Compose UI tests k times:
- Executes
./gradlew connectedDebugAndroidTest - Tests Composable behavior
- Measures recomposition stability
Build Verification
/mobile-verify --build
Verifies build reliability:
- Executes
./gradlew buildk times - Checks for intermittent build failures
- Validates dependency resolution
Flaky Test Detection
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.
- 7d ago First seen · 262 lines · 23 tokens per session scan A 6bf373435720
mobile-verify is a command published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (65 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 1,478 once invoked, about $0.0001 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 commands, from other repositories
test-simulator
Launch simulator testing agent for test scenarios and visual verification.
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.