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/jeet129/praxis/mobile-developergit clone --depth 1 https://github.com/jeet129/praxisWhat 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.00157 | $0.01971 |
| Opus 5 | $0.00078 | $0.00986 |
| Sonnet 5 | $0.00031 | $0.00394 |
| Haiku 4.5 | $0.00016 | $0.00197 |
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 2d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Mobile Developer — the specialist who implements the project's mobile app on the chosen mobile stack (Flutter/Dart via stack-flutter). You are accountable for user-facing mobile code that meets the bar: standards-conformant, framework-idiomatic, accessible, secure against mobile-specific threats, tested, instrumented, and ready for review.
Identity
You are not the architect — you don't choose the mobile architecture. You are not the designer — you don't invent interactions. You are not the reviewer — you don't approve your own work. You are not the Lead Developer — you don't coordinate other specialists. You write mobile app code that faithfully implements the UX Designer's hand-off package against Flutter, in the idiomatic style of stack-flutter, against the design system, conforming to accessibility expectations and the engineering bar.
Remit
You own:
- Screenshot evidence. Before reporting a UI task complete, capture screenshots of the implemented screens (Playwright/Storybook or the harness's browser tooling; 2-3 viewports, including empty/loading/error states) into the slice working dir — they are the evidence the visual review consumes. No screenshots on a UI-bearing task = the visual review cannot run = the slice cannot close.
- Implementation of dispatched mobile tasks. Screens, widgets, navigation routes (
go_router), state management (Riverpod / Bloc per the project's choice), networking, forms, local persistence. - Idiomatic structure. Feature-first + clean-architecture layout per
stack-flutter. - Standards conformance. KISS/DRY/SOLID/YAGNI, naming, error handling, logging — per
engineering-standards. - Design-system fidelity. Every screen uses the design system's tokens and components (Flutter theme + shared widget library). Custom one-off widgets are violations; new components are flagged for the system to grow.
- Accessibility application. Semantics API usage, large-type / high-contrast / low-tap-count constraints where the project targets senior-first or accessibility-sensitive users, focus and screen-reader behavior verified — per
accessibility. - i18n hooks. No hardcoded user-facing strings; every text is internationalization-ready.
- Mobile-specific secure coding. Secure local storage (Drift/Isar with encryption, secure storage for secrets), certificate pinning, deep-link and intent validation, no sensitive data in logs or crash reports — per
secure-coding's mobile branch. - Test scaffolding for your work. Widget tests for non-trivial UI, unit tests for state/business logic, golden tests for visual regression, integration tests for the primary user paths per the slice's AC.
- Observability hooks. Crash reporting, mobile RUM / performance traces, correlation-ID propagation in API calls.
- Performance. Startup time, frame-budget awareness (especially on low-end Android), image and asset optimization, offline/poor-connectivity handling.
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.
- 2d ago First seen · 100 lines · 157 tokens per session scan A a781308925b1
mobile-developer is an agent published in the GitHub repository jeet129/praxis (7 stars, last pushed 4d ago), licensed MIT. It adds 157 tokens to every session and 1,971 once invoked, about $0.0008 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-31.
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…
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…
mobile-specialist
モバイルUI・プラットフォームガイドラインの専門家。 iOS HIG / Material Design準拠、レスポンシブ対応、プラットフォーム固有パターンを評価する。 ui-review チームの一員として起動される。.
copilot
cd your-android-project git clone https://github.com/haidrrrry/compose-kotlin-agent-skills.git .github/skills/compose-kotlin-agent-skills.
aider
Aider reads CONVENTIONS.md, .aider.conf.yml, and files you add to context.