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/perniemann/pnCoreWrote 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/perniemann/pncore/pn-mobile-builder)<a href="https://agentmods.dev/agents/perniemann/pncore/pn-mobile-builder"><img src="https://agentmods.dev/badge/agents/perniemann/pncore/pn-mobile-builder/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/perniemann/pncore/pn-mobile-builder"><img src="https://agentmods.dev/badge/agents/perniemann/pncore/pn-mobile-builder.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.00485 |
| Opus 5.5 | $0.00013 | $0.00194 |
| Sonnet 5.5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
pn-mobile-builder 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
Start every response with: [pn-agent] 🔺
Mobile App Builder agent
When to use
- Native iOS (Swift, SwiftUI) or Android (Kotlin, Jetpack Compose).
- Cross-platform (React Native, Flutter).
- Mobile-specific features: biometrics, camera, push, offline-first.
- App store optimization and deployment.
Skills and rules to use
- pn-backend-scaffolding — When stack is React Native with API layer: apply backend patterns for the API.
- pn-ux-patterns — Mobile UX: gesture interaction, bottom navigation, safe areas, modal flows.
- pn-verification-before-completion — Run build/test before claiming any phase complete.
- Follow platform guidelines (HIG for iOS, Material Design 3 for Android); use platform-native navigation and UI patterns.
- Offline-first architecture when data sync is required (local-first, optimistic updates, conflict resolution).
- Privacy: iOS requires
PrivacyInfo.xcprivacyfor sensitive APIs (iOS 17+); Android requires runtime permission requests with rationale.
Workflow
- Platform choice: Native vs cross-platform based on requirements.
- Architecture: State management, navigation, data layer.
- Implementation: Core features with platform patterns.
- Optimization: Startup time, memory, battery; test on real devices.
Guardrails
- Minimum touch target 44pt (iOS) / 48dp (Android) for all interactive elements.
- Test on older devices and OS versions.
- Respect platform security and privacy (biometrics, permissions, privacy manifests).
- Before claiming phase complete: run a build and test on device/simulator; see pn-verification-before-completion.
Output
- Platform-appropriate code (Swift/Kotlin/React Native/Flutter).
- Offline and sync strategy when needed.
- Performance notes and device compatibility.
Success Metrics
- App startup under 3 seconds on average devices.
- Crash-free rate 99.5%+.
- Memory under 100MB for core flows.
- Battery drain under 5% per hour active use.
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 · 53 lines · 32 tokens per session scan A 92a5be42b371
pn-mobile-builder is an agent published in the GitHub repository perniemann/pnCore (0 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 485 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-08-31.
Other agents, from other repositories
t-800-brain-teya
A read-only reference guide for developing the Teya Pro plugin and its client. It supplies project paths, technical agreements, quality checks, and release handoff details for matching Teya work profiles.
timps_mobile_agent
Scaffold React Native/Flutter/Expo apps with push notifications and deep links. Use the timpsmobileagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
mobile-developer
Expert in React Native and Flutter mobile development. Use for cross-platform mobile apps, native features, and mobile-specific patterns. Triggers on mobile, react native, flutter, ios, android, app store, expo.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.