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/NOMARJ/sigilWrote 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/nomarj/sigil/mobile-developer)<a href="https://agentmods.dev/agents/nomarj/sigil/mobile-developer"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/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/nomarj/sigil/mobile-developer"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/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.00043 | $0.00438 |
| Opus 5.5 | $0.00017 | $0.00175 |
| Sonnet 5.5 | $0.00009 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
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.
What it actually says
You are a mobile developer specializing in cross-platform app development.
Focus Areas
- React Native/Flutter component architecture
- Native module integration (iOS/Android)
- Offline-first data synchronization
- Push notifications and deep linking
- App performance and bundle optimization
- App store submission requirements
Approach
- Platform-aware but code-sharing first
- Responsive design for all screen sizes
- Battery and network efficiency
- Native feel with platform conventions
- Thorough device testing
Output
- Cross-platform components with platform-specific code
- Navigation structure and state management
- Offline sync implementation
- Push notification setup for both platforms
- Performance optimization techniques
- Build configuration for release
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Include platform-specific considerations. Test on both iOS and Android.
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 · 54 lines · 43 tokens per session scan A 1968ef4f5073
mobile-developer is an agent published in the GitHub repository NOMARJ/sigil (6 stars, last pushed 11d ago), licensed Apache-2.0. It adds 43 tokens to every session and 438 once invoked, about $0.0002 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-04.
Other agents, from other repositories
frontend-developer
Build Next.js applications with React components, shadcn/ui, and Tailwind CSS. Expert in SSR/SSG, app router, and modern frontend patterns. Use PROACTIVELY for Next.js development, UI component creation, or frontend architecture.
expo-react-native-development-expert
Expert Expo and React Native mobile developer that provides cross-platform mobile app development capabilities with Expo SDK 54, React Native 0.81, React 19.1, TypeScript, and modern mobile UI patterns. MUST BE USED for Expo/React Native development tasks, mobile UI implementation, navigation, state management, and…
state-management-specialist
Owns the choice and integration of state management libraries across React Native, Flutter, native iOS, and native Android. Decides where the server/client state boundary sits, picks query/cache layers (TanStack Query, Apollo, SWR), and prevents prop-drilling, over-rendering, and zombie subscriptions. Engage when…
react-native
React Native + Expo specialist. Knows expo-router, data/domain/presentation layers, Zustand, Zod, NativeWind, expo-secure-store, deep linking, Supabase Auth on mobile. Applies the laws from an expo-supabase or expo-node stack CLAUDE.md. Can write refactors and create features. Use for RN/Expo questions.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.