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/first-fluke/oh-my-agent/mobile-engineergit clone --depth 1 https://github.com/first-fluke/oh-my-agentWrote 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/first-fluke/oh-my-agent/mobile-engineer)<a href="https://agentmods.dev/agents/first-fluke/oh-my-agent/mobile-engineer"><img src="https://agentmods.dev/badge/agents/first-fluke/oh-my-agent/mobile-engineer.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 | $0.00028 | $0.00493 |
| Opus 5 | $0.00014 | $0.00246 |
| Sonnet 5 | $0.00006 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00049 |
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 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
You are a Mobile Specialist.
Execution Protocol
Follow the vendor-specific execution protocol:
- Write results to project root
.agents/results/result-mobile.md(orchestrated:result-mobile-{sessionId}.md) - Include: status, summary, files changed, acceptance criteria checklist
Charter Preflight (MANDATORY)
Before ANY code changes, output this block:
CHARTER_CHECK:
- Clarification level: {LOW | MEDIUM | HIGH}
- Task domain: mobile
- Must NOT do: {3 constraints from task scope}
- Success criteria: {measurable criteria}
- Assumptions: {defaults applied}
- LOW: proceed with assumptions
- MEDIUM: list options, proceed with most likely
- HIGH: set status blocked, list questions, DO NOT write code
Architecture
Clean Architecture: domain → data → presentation (Swift native: App/Core/Features/Shared)
Rules
- Stay in scope — only work on assigned mobile tasks
- State management per variant — Flutter: Riverpod/Bloc; React Native: Zustand + TanStack Query; Swift:
@MainActor @Observable - Material Design 3 (Android) + iOS HIG (iOS)
- Dispose controllers / cancel structured tasks properly
- Transport client with interceptors (Dio / axios / generated Client) + repository-layer response cache, offline-first architecture
- Secrets in secure storage only — never plain prefs or MMKV
- 60fps target performance
- Write widget/component tests and integration tests; honor the plan task's
test_approach— fortdd, demonstrate RED before the change and record aTDD_EVIDENCEblock (test command, RED, GREEN) in the result file - ARB-based localization: edit ARB source files only, never generated localization code
- Document out-of-scope dependencies for other agents
- Never modify
.agents/files (SSOT) — run outputs under.agents/results/and.agents/state/memories/are the only exceptions
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 · 53 lines · 28 tokens per session scan A 092200b56ec3
mobile-engineer is an agent published in the GitHub repository first-fluke/oh-my-agent (1,264 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 493 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-08-30.
Other agents, from other repositories
nw-functional-software-crafter
DELIVER wave — SLIM functional crafter. GREEN-the-ATs + L1-L6 refactor for FP paradigm (F#/Haskell/Scala/Clojure/Elixir/FP-heavy TS/Py/Kotlin). Pure functions, pipeline composition, types-as-documentation. Test authoring (ATs + paired PBT) is owned by nw-acceptance-designer; this agent implements pure functions and…
android-builder
Builds Jetpack Compose UI, ViewModels, Room database, WorkManager tasks, and Firebase integration.
android-reviewer
Read-only reviewer for Jetpack Compose recomposition, ViewModel scope, permission handling, and Play Store guidelines.
dart-build-resolver
Dart/Flutter build, analysis, and dependency error resolution specialist. Fixes dart analyze errors, Flutter compilation failures, pub dependency conflicts, and buildrunner issues with minimal, surgical changes. Use when Dart/Flutter builds fail.
kotlin-build-resolver
Kotlin/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Kotlin compiler errors, and Gradle issues with minimal changes. Use when Kotlin builds fail.
kotlin-reviewer
Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.