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.
git 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-quality-gate)<a href="https://agentmods.dev/commands/ahmed3elshaer/everything-claude-code-mobile/feature-quality-gate"><img src="https://agentmods.dev/badge/commands/ahmed3elshaer/everything-claude-code-mobile/feature-quality-gate.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.00444 |
| Opus 5 | $0.00012 | $0.00222 |
| Sonnet 5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
feature-quality-gate 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 4d 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 Quality Gate Command
Phase 5 of the feature build pipeline. Runs parallel quality reviews, collects findings, applies fixes, and re-verifies critical issues.
Usage
/feature-quality-gate auth
/feature-quality-gate offline-cache
/feature-quality-gate push-notifications
Parallel Reviews
Three review agents run simultaneously:
Code Review
android-reviewer(Android) /ios-reviewer(iOS)- Kotlin/Swift style compliance
- Pattern adherence (MVI/MVVM, Compose/SwiftUI conventions)
- Error handling completeness
- API surface cleanliness
Security Audit
mobile-security-reviewer- No hardcoded secrets or API keys
- Proper encryption for stored data
- HTTPS-only network calls, certificate pinning
- Secure token storage (Keystore / Keychain)
- Input validation and sanitization
Performance Review
mobile-performance-reviewer- Compose recomposition efficiency / SwiftUI view identity
- Memory leak detection (retained references, unclosed streams)
- Startup impact analysis
- Network call optimization (batching, caching headers)
Workflow
- All three reviews run in parallel
- Findings collected and deduplicated
- Fixes applied automatically where possible
- Critical findings re-verified after fix
Severity Levels
| Severity | Action | Example |
|---|---|---|
| Critical | Must fix before proceeding | Hardcoded API key, memory leak |
| Warning | Should fix, non-blocking | Missing null check, suboptimal recomposition |
| Info | Nice to have | Naming suggestion, minor style nit |
Output
Quality report appended to .omc/state/feature-{name}.json with findings count per severity and review pass/fail status.
Invokes
android-reviewer/ios-revieweragentmobile-security-revieweragentmobile-performance-revieweragent
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.
- 4d ago First seen · 67 lines · 24 tokens per session scan A 04c91caf8ea6
feature-quality-gate is a command published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (66 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 444 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
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
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.
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.