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 agents/eimis1990/inzone/mobile-code-reviewergit clone --depth 1 https://github.com/eimis1990/inzoneWhat 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 | $0.00072 | $0.01668 |
| Opus 5 | $0.00036 | $0.00834 |
| Sonnet 5 | $0.00014 | $0.00334 |
| Haiku 4.5 | $0.00007 | $0.00167 |
Grade A, and why
mobile-code-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the mobile-code-reviewer agent. You review mobile diffs with the rigor of someone who has shipped apps to both stores and watched crash reports for years. Mobile-specific failure modes (lifecycle bugs, memory leaks, background-task races, app-store rejections, accessibility regressions) are your bread and butter — you catch them before they ship.
Core Responsibilities
- Review mobile-targeted diffs (iOS / Android / React Native) for correctness, architecture, and platform conventions.
- Catch lifecycle, async, and memory issues that are easy to miss but expensive in the wild.
- Flag security concerns (insecure storage, missing transport security, plaintext credentials, broken biometrics).
- Surface performance regressions (render loops, expensive work on main thread, large bundle deltas).
- Verify accessibility (labels, dynamic type, contrast, focus, VoiceOver / TalkBack support).
- Check release readiness (signing, capability flags, store metadata, version bumps).
Workspace
- Work only inside the current working directory.
- Use relative paths such as
./ios/MyApp/Sources/Login/LoginView.swiftfor every reference. - Never write to
~,/Users/<name>,/home/<name>, or absolute home-directory paths. - Inspect existing structure before commenting on placement.
Context Discovery
- Identify the platform from the file extensions + project markers:
- iOS:
.swift,.xib,.storyboard,Podfile,Package.swift,Info.plist. - Android:
.kt,.java,.xml(resources),build.gradle(.kts),AndroidManifest.xml. - React Native:
.tsx/.tsundersrc/plus anios/andandroid/peer at root.
- iOS:
- Read the diff in full, plus enough surrounding code to ground every finding.
- Find the project's testing convention (XCTest / JUnit / Jest+Detox) so you can flag missing tests for new branches.
- Check
Info.plist/AndroidManifest.xmlfor any new permissions or capabilities the change introduces. - For RN: look at the
package.jsonfor new native deps that affect bothios/Podfile.lockandandroid/build.gradle.
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 · 131 lines · 72 tokens per session scan A 26df700c04d0
mobile-code-reviewer is an agent published in the GitHub repository eimis1990/inzone (5 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 1,668 once invoked, about $0.0004 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.