mobile-engineer

Install

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.

agentmods

npx agentmods add agents/first-fluke/fullstack-starter/mobile-engineer

Clone the repo

git clone --depth 1 https://github.com/first-fluke/fullstack-starter

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/mobile-engineer.svg)](https://agentmods.dev/agents/first-fluke/fullstack-starter/mobile-engineer)

Your own site

<a href="https://agentmods.dev/agents/first-fluke/fullstack-starter/mobile-engineer"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/mobile-engineer.svg" alt="Measured on agentmods" height="20"></a>

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 493 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin unknown No closer match found in the catalogue.

Token cost

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

Measured today against content hash 092200b56ec3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 today.

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.

.agents/agents/mobile-engineer.md · 53 lines

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 — for tdd, demonstrate RED before the change and record a TDD_EVIDENCE block (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

Changes

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.

today First seen · 53 lines · 28 tokens per session scan A 092200b56ec3

Subscribe to this mod's changes

mobile-engineer is an agent published in the GitHub repository first-fluke/fullstack-starter (222 stars, last pushed 3d ago), 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-09-03.

Frontend Mobile fastapi flutter gcp mise monorepo nextjs

flutter-engineer

Use this agent when building Flutter applications with Dart 3.11, Riverpod 3, GoRouter 17, Material 3, Freezed 3, Dio 5, and all 6 platform targets (iOS, Android, Web, macOS, Windows, Linux).

altmemy/claude-code-templates · 62 tokens

flutter-integration-analyzer

Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…

JayCRL/MobileVC · 429 tokens

spec-auditor

Audits a change to the dev-challenge spec layer before it is committed — checks specs against the OpenAPI contract, criterion IDs against harness coverage, and internal consistency across specs, code and fixtures. Use when specs/ has been edited, when API behaviour changed, or when spec-drift CI is failing and the…

micheltlutz/dev-challenge · 73 tokens