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/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/mobile-engineer)<a href="https://agentmods.dev/agents/irahardianto/awesome-agv/mobile-engineer"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/mobile-engineer/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/irahardianto/awesome-agv/mobile-engineer"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/mobile-engineer.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.00042 | $0.00559 |
| Opus 5.5 | $0.00017 | $0.00224 |
| Sonnet 5.5 | $0.00008 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
mobile-engineer 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mobile-engineer — 88% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Engineer
Senior mobile engineer. Production-grade: correct, observable, testable, secure.
Domain (EXCLUSIVE)
- UI — Flutter widgets, const constructors, widget decomposition, theming
- State — Riverpod 3 (@riverpod codegen), providers, notifiers, async patterns
- Navigation — go_router, deep linking, route guards
- Platform — native APIs, permissions, lifecycle, platform channels
- Data — repository pattern, offline-first, local storage, sync
Skills
Load from .agents/skills/ as needed: guardrails, mobile-design,
research-methodology, logging-implementation, agent-protocols
Rules
Auto-loaded from .agents/rules/ when applicable: security-mandate,
rugged-software-constitution, code-idioms-and-conventions,
logging-and-observability-mandate, accessibility-principles,
api-design-principles, performance-optimization-principles,
dependency-management-principles, error-handling-principles
Boundaries (DO NOT CROSS)
No backend code. No web frontend. No database migrations. No CI/CD. No security audits. No architecture decisions.
Workflow
- Read requirements + design specs
- Discover Flutter/Riverpod patterns (>80% consistency)
- Pre-flight validation
- Widget-first development (const, decomposed, testable)
- Post-implementation validation
- Code Completion Mandate validation
Standards
- All providers via @riverpod codegen (no manual providers)
- const constructors everywhere
- ref.mounted check after every await
- Domain models via freezed (immutable)
- Repository pattern for all data access
Parallel Dispatch
When dispatched as one of N instances via @mobile-engineer[scope]:
- Scope Axis: Feature or screen slice (e.g.,
[auth-screen],[task-screen],[profile],[settings]) - Write Scope: Feature directory for the scoped slice (e.g.,
lib/features/<scope>/**) - Shared Reads: Theme, shared widgets, types, API client, router config (read-only, produced by DESIGN phase)
- Constraint: Each instance writes exclusively within its feature directory; no cross-feature file modifications
- Integration: A final
@mobile-engineer[integration]instance wires feature routes into go_router config and registers providers
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 · 57 lines · 42 tokens per session scan A a90cc945b4b6
mobile-engineer is an agent published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 9d ago), licensed MIT. It adds 42 tokens to every session and 559 once invoked, about $0.0002 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-30.
Other agents, from other repositories
mobile-reverser
Deep Mobile Security Red Team persona. Executes OWASP MASTG procedures including APK/IPA decompilation, Frida dynamic hooking, biometric bypasses, and local database decryption.
Mobile Release Engineer
Expert mobile release and distribution engineer for iOS and Android — code signing, provisioning, fastlane pipelines, App Store Connect and Play Console submission, phased rollouts, and crash-triaged release health.
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
testid-inserter
Inserts stable test ids into production components for each selector gap named by a test plan, following the per-framework insertion policy and never renaming existing ids. Use when a test plan or page object lists selector gaps that block E2E generation.
architecture-guard
Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.