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 commands/ahmed3elshaer/everything-claude-code-mobile/feature-verifygit 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/feature-verify)<a href="https://agentmods.dev/commands/ahmed3elshaer/everything-claude-code-mobile/feature-verify"><img src="https://agentmods.dev/badge/commands/ahmed3elshaer/everything-claude-code-mobile/feature-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.00024 | $0.00464 |
| Opus 5 | $0.00012 | $0.00232 |
| Sonnet 5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
feature-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 2d 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
Feature Verify Command
Phase 6 of the feature build pipeline. Final verification gate that confirms the feature is production-ready through repeated test runs and coverage analysis.
Usage
/feature-verify auth
/feature-verify offline-cache
/feature-verify push-notifications
Verification Steps
- pass@k Testing (k=3):
mobile-verifierruns the full test suite 3 times to detect flakiness - Coverage Report: Generates coverage using platform tooling
- Android: Kover (
./gradlew koverHtmlReport) - iOS: xcov (
xcrun xccov)
- Android: Kover (
- Threshold Check: Validates coverage meets the 80% minimum
- Sign-off Report: Produces final summary with pass/fail determination
Thresholds
| Metric | Threshold | Action if Below |
|---|---|---|
| pass@k | >= 0.9 (90%) | Flaky tests must be fixed or quarantined |
| Coverage | >= 80% | Missing tests must be added |
Output
Feature Verification: auth
══════════════════════════
pass@k (k=3):
Unit Tests: 45/45 (100%) ✓
UI Tests: 18/18 (100%) ✓
E2E Tests: 5/6 (83%) ⚠ 1 flaky
Coverage:
ViewModel: 98% ✓
UseCase: 100% ✓
Repository: 91% ✓
UI: 84% ✓
Overall: 88% ✓
Flaky Tests:
- AuthE2ETest.testBiometricFallback (2/3 passes)
Sign-off: PASS (with 1 flaky test noted)
Report Location
Final report written to .omc/state/feature-{name}.json under the verification key.
Invokes
mobile-verifieragent
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.
- 2d ago First seen · 63 lines · 24 tokens per session scan A 5ef4908a8aa8
feature-verify is a command published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (65 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 464 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-09-03.
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.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
feat
Kick off tasks creation for a new feature (4-item interview before invoking pm-agent; an epic-sized requirement routes to phased decomposition, a feature already built on one platform routes to cross-platform parity, a change that touches no endpoint routes to client-only).
status
Project health dashboard - shows environment status and suggests improvements.
checklist
Generate a custom checklist for the current feature based on user requirements.