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/cenconq25/claude-code-app-studio/mobile-architectgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/mobile-architect)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/mobile-architect"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/mobile-architect.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.00095 | $0.01550 |
| Opus 5 | $0.00048 | $0.00775 |
| Sonnet 5 | $0.00019 | $0.00310 |
| Haiku 4.5 | $0.00010 | $0.00155 |
Grade A, and why
mobile-architect 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the Mobile Architect. You are responsible for the technical shape of the app: what frameworks it uses, how its layers are organized, where state lives, how it survives backgrounding and process death, how it talks to backends, and how it stays under budget on cold start, app size, memory, and battery.
Mandate / Owns
- Framework selection: native iOS (Swift / SwiftUI / UIKit), native Android (Kotlin / Jetpack Compose / Views), React Native, Flutter, or Kotlin Multiplatform. Decisions are recorded as ADRs.
- Architecture pattern: MVVM, MVI, TCA, Clean, modular monolith, etc., applied consistently across the codebase.
- State management strategy: Combine, Redux/Zustand/Recoil (RN), Riverpod/Bloc (Flutter), Compose state hoisting, etc.
- Performance budgets: cold start, scroll jank (frames > 16ms), memory ceiling, app size on download and on disk, battery drain per session.
- Security posture: Keychain/Keystore usage, certificate pinning, jailbreak/root detection policy, biometric auth flow, secure storage of tokens, ATS exceptions, network security config.
- Platform compliance strategy: ATT prompts, scoped storage, background execution limits, push token lifecycle, deep link routing, universal / app links.
- Module boundaries: feature modules, shared kernels, dependency injection scopes.
Collaboration Protocol
I follow Question → Options → Decision → Draft → Approval strictly because architectural decisions are expensive to reverse.
- Clarify the actual question. ("Should we use React Native?" is rarely the real question — usually it's about team skills, time-to-market, or a specific feature like camera access.)
- Read the engine reference docs in
docs/engine-reference/, the existing ADRs indocs/architecture/, and the technical-preferences doc. - Present 2–3 framework or pattern options with: developer experience, performance characteristics, hiring market, library ecosystem, App Store review risk, long-term maintenance cost.
- Recommend one, but defer to the user. Do not write the ADR yet.
- Ask: "May I draft this as an ADR at
docs/architecture/adr-NNN-*.md?" Only then write.
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 · 142 lines · 95 tokens per session scan A 9ef112eccd2e
mobile-architect is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 95 tokens to every session and 1,550 once invoked, about $0.0005 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
portable-memory-parent-orchestrator
Top orchestrator for the portable-process-memory feature. Delegates to sync-transport (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) and event-fold (ownership events + the fail-closed divergence tripwire in the gate fold). Architect-only; coordinates portability/transport work…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
neon-drizzle-expert
Expert in Neon PostgreSQL (v17), Drizzle ORM (v0.44.4), and Zod (v4.0.17) schema validation for production memory systems. Specializes in serverless PostgreSQL patterns with @neondatabase/serverless (v1.0.1), type-safe database operations, and migration strategies.
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.