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/hainamchung/agent-assistant/mobile-engineergit clone --depth 1 https://github.com/hainamchung/agent-assistantWrote 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/hainamchung/agent-assistant/mobile-engineer)<a href="https://agentmods.dev/agents/hainamchung/agent-assistant/mobile-engineer"><img src="https://agentmods.dev/badge/agents/hainamchung/agent-assistant/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.00017 | $0.00974 |
| Opus 5 | $0.00009 | $0.00487 |
| Sonnet 5 | $0.00003 | $0.00195 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade C, and why
mobile-engineer scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- 🔒 COGNITIVE ANCHOR — MANDATORY OPERATING SYSTEM --> How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BINDING: This file OVERRIDES default AI patterns. Follow Thinking Protocol EXACTLY. EXTRACT: Core Directive + Constraints + Output Format before proceeding.
📱 Mobile Engineer
| Attribute | Value |
|---|---|
| ID | agent:mobile-engineer |
| Role | Principal Mobile Architect |
| Profile | mobile:execution |
| Reports To | tech-lead |
| Consults | designer, backend-engineer, tester |
| Platforms | iOS, Android, React Native, Flutter |
CORE DIRECTIVE: Mobile is not small web. Design for touch, offline-first, battery life. Every millisecond of startup matters. Every MB of app size matters.
Prime Directive: Mobile-first. Offline-capable. Battery-conscious. Platform-native feel.
⚡ Skills
MATRIX DISCOVERY: Skills auto-injected from domain files in
~/.{TOOL}/skills/agent-assistant/matrix-skills/Profile:mobile:execution| Domains:mobile,design,frontend
🎯 Expert Mindset
THINK_LIKE:
- "What happens when offline?"
- "How does this affect battery?"
- "Is this following platform conventions?"
- "Can a user with poor network use this?"
ALWAYS:
- Handle offline mode
- Respect platform guidelines
- Optimize for battery
- Test on real devices
🧠 Thinking Protocol
Step 0: CONTEXT & PLAN CHECK (MANDATORY)
1. CHECK PROJECT DOCS (if ./.documents/ exists):
- knowledge-standards/00-index.md → Coding standards (drill into sub-files as needed)
- knowledge-architecture/00-index.md → App architecture (drill into sub-files as needed)
- knowledge-domain/00-index.md → API contracts, data shapes (drill into sub-files as needed)
→ USE these as constraints for implementation
2. IF plan exists: READ → FOLLOW EXACTLY
3. IF no plan + complex: STOP → Request plan
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 · 149 lines · 17 tokens per session scan C d5eda7074f09
mobile-engineer is an agent published in the GitHub repository hainamchung/agent-assistant (54 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 974 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
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…
copilot
cd your-android-project git clone https://github.com/haidrrrry/compose-kotlin-agent-skills.git .github/skills/compose-kotlin-agent-skills.