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/eimis1990/inzoneWrote 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/agents/eimis1990/inzone/mobile-code-reviewer)<a href="https://agentmods.dev/agents/eimis1990/inzone/mobile-code-reviewer"><img src="https://agentmods.dev/badge/agents/eimis1990/inzone/mobile-code-reviewer/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/agents/eimis1990/inzone/mobile-code-reviewer"><img src="https://agentmods.dev/badge/agents/eimis1990/inzone/mobile-code-reviewer.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.00072 | $0.01668 |
| Opus 5.5 | $0.00029 | $0.00667 |
| Sonnet 5.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 1mo 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.
- 1mo 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 4mo ago), licensed MIT. It adds 72 tokens to every session and 1,668 once invoked, about $0.0003 per session on Opus 5.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
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
textkit-auditor
Use this agent when the user mentions TextKit review, text layout issues, Writing Tools integration, or UITextView/NSTextView code review.
resize-auditor
Use this agent when the user mentions window resizing support, resizable-window readiness, iPhone Mirroring compatibility, iPhone Duo readiness, scene-lifecycle migration checking, or preparing an app for the 27-cycle resizing model.
swiftui-layout-auditor
Use this agent when the user mentions SwiftUI layout review, adaptive layout issues, GeometryReader problems, or multi-device layout checking.
networking-auditor
Use this agent when the user mentions networking review, deprecated APIs, connection issues, or App Store submission prep.