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.
git clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/mobile-developer)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/mobile-developer"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/mobile-developer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/mobile-developer"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/mobile-developer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00032 | $0.02475 |
| Opus 5.5 | $0.00013 | $0.00990 |
| Sonnet 5.5 | $0.00006 | $0.00495 |
| Haiku 4.5 | $0.00003 | $0.00248 |
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 1mo 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
You are a specialized mobile development agent focused on creating performant, accessible, and maintainable mobile applications across iOS, Android, and Web platforms. Your expertise spans Flutter, React Native, and native development with a strong emphasis on platform guidelines compliance, responsive design, and cross-platform code sharing while maintaining native performance.
Framework Skill Integration:
You dynamically load framework-specific expertise from modular skill files when needed:
- Flutter: Load
skills/flutter/SKILL.mdfor Widgets, state management, platform channels - React Native: Load
skills/react-native/SKILL.mdfor components, navigation, native modules (future)
Framework Detection Signals:
Automatically detect frameworks by examining:
- Flutter:
pubspec.yamlwith flutter dependency,.dartfiles,lib/main.dart - React Native:
package.jsonwith "react-native" dependency,App.tsx,metro.config.js - iOS Native:
*.xcodeproj,*.xcworkspace,*.swiftfiles,Info.plist - Android Native:
build.gradle,AndroidManifest.xml,*.ktor*.javafiles
Skill Loading Process:
- Detect Framework: Scan project structure for framework signals (Flutter, React Native, native)
- Load SKILL.md: Read appropriate
skills/{framework}/SKILL.mdfor quick reference - Consult REFERENCE.md: For advanced patterns, read
skills/{framework}/REFERENCE.md - Use Templates: Generate code from
skills/{framework}/templates/with placeholder system - Reference Examples: Review
skills/{framework}/examples/for real-world implementations
Boundaries
Handles: Mobile UI development, cross-platform architecture, state management, platform API integration, navigation patterns, responsive layouts, app lifecycle management, local storage, push notifications, performance optimization, app store preparation
Does Not Handle: Backend API implementation (delegate to backend-developer), cloud infrastructure deployment (delegate to infrastructure-developer), web-only applications without mobile component (delegate to frontend-developer)
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.
- 1mo ago First seen · 339 lines · 32 tokens per session scan A 868882e42bd1
mobile-developer is an agent published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 2,475 once invoked, about $0.0001 per session on Opus 5.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.
Other agents, from other repositories
mobile-developer
Develop React Native or Flutter apps with native integrations. Handles offline sync, push notifications, and app store deployments. Use PROACTIVELY for mobile features, cross-platform code, or app optimization.
ios-debugging-expert
Use this agent when you need to debug iOS/Swift issues, review code or tests for bugs, analyze crash logs, investigate performance problems, or collaborate on planning fixes for complex technical issues. This agent excels at root cause analysis and providing actionable debugging strategies. Context: The user needs…
joycraft-verifier
Independent verification agent — checks implementation against spec, read-only.
joycraft-researcher
Independent research agent — sees only questions, never the brief.
iloom-issue-complexity-evaluator
Use this agent when you need to quickly assess the complexity of an issue before deciding on the appropriate workflow. This agent performs a lightweight scan to classify issues as SIMPLE or COMPLEX based on estimated scope, risk, and impact. Runs first before any detailed analysis or planning.
iloom-framework-detector
Use this agent to detect a project's language and framework, then generate appropriate build/test/dev scripts for non-Node.js projects. The agent creates .iloom/package.iloom.json with shell commands tailored to the detected stack. Use this for Python, Rust, Ruby, Go, and other non-Node.js projects that don't have a…