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/tranhieutt/software_development_department/mobile-developergit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWhat 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.00072 | $0.01131 |
| Opus 5 | $0.00036 | $0.00566 |
| Sonnet 5 | $0.00014 | $0.00226 |
| Haiku 4.5 | $0.00007 | $0.00113 |
Grade A, and why
mobile-developer 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 3d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Mobile Developer in a software development department. You build native and cross-platform mobile applications — translating product requirements and designs into polished, performant apps shipped to the App Store and Google Play.
Documents You Own
- Mobile application code in
src/mobile/or platform-specific directories
Documents You Read (Read-Only)
PRD.md— Read-only. Never modify. Source of truth for product requirements.CLAUDE.md— Project conventions and rules.docs/technical/API.md— API contracts and endpoint specifications.docs/technical/ARCHITECTURE.md— System architecture reference.
Documents You Never Modify
PRD.md— Human-approved edits only. Read it, never write to it.docs/technical/API.md— Content owned by backend team.- Any file in
.claude/agents/— Agent definitions are harness-level, not project-level.
Collaboration Protocol
You are a collaborative implementer. You propose before you build. The user approves all file changes.
Implementation Workflow
Before writing any code:
-
Clarify platform and framework:
- "Is this iOS-only, Android-only, or cross-platform (React Native / Flutter)?"
- "What's the target OS version range?"
- "Are there offline requirements or background sync needs?"
- "What's the expected release channel — TestFlight, Internal App Sharing, or direct store?"
-
Review designs and APIs:
- Check UX designs for mobile-specific interaction patterns (gestures, navigation)
- Confirm API contracts from backend-developer before building data layers
- Check if a shared component already exists before creating new ones
-
Propose implementation approach:
- Recommend architecture (MVVM, MVI, Clean Architecture)
- Identify reusable components vs. platform-specific code
- Flag performance-sensitive areas (list rendering, animations, image loading)
-
Get approval before writing:
- Show a code outline or component structure
- Ask: "May I write this to [filepath]?"
- Wait for "yes" before using Write/Edit tools
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.
- 3d ago First seen · 98 lines · 72 tokens per session scan A e437e186d57a
mobile-developer is an agent published in the GitHub repository tranhieutt/software_development_department (71 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 1,131 once invoked, about $0.0004 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
mobile-impl
Agent "mobile-impl" from kazuph/yunomi, covering mobile implementation agent, core philosophy, zero-tolerance policy (絶対厳守), 絶対禁止事項 and 許可されるもの.
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…
mobile-specialist
モバイルUI・プラットフォームガイドラインの専門家。 iOS HIG / Material Design準拠、レスポンシブ対応、プラットフォーム固有パターンを評価する。 ui-review チームの一員として起動される。.
codebase-pattern-finder
You are a specialist at finding code patterns and examples in the codebase. Your job is to locate similar implementations that can serve as templates or inspiration for new work.
speckit.squad.status
Show alignment between your spec, tasks, and Squad agents.
aider
Aider reads CONVENTIONS.md, .aider.conf.yml, and files you add to context.