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 skills add suntay44/buildable-plugin-skills --skill mobile-buildergit clone --depth 1 https://github.com/suntay44/buildable-plugin-skillsWrote 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/skills/suntay44/buildable-plugin-skills/mobile-builder)<a href="https://agentmods.dev/skills/suntay44/buildable-plugin-skills/mobile-builder"><img src="https://agentmods.dev/badge/skills/suntay44/buildable-plugin-skills/mobile-builder.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.00565 |
| Opus 5 | $0.00029 | $0.00282 |
| Sonnet 5 | $0.00012 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
buildable-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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- buildable-mobile-builder — 86% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Buildable Mobile Builder Skill
Use this skill to generate or adapt local mobile prototypes.
Resolve all referenced paths from the Buildable plugin or repository root.
Reference Loading Contract
Mandatory order:
- Read the saved planner output first:
.buildable/phase-plan.jsonwhen present, otherwisebuildable-app-spec.json. Use.buildable/phase-plan.toonwhen present as the compact agent-facing build contract. - Load only
appSpec.references. - Load current project files only as needed for the requested change.
- Do not load web templates or unrelated mobile archetypes.
- Load starter source only for the selected template and only when generating or editing it.
Default Stack
- Expo
- React Native
- TypeScript
- NativeWind
- Expo Router when appropriate
- local/mock data
Workflow
- Read the saved plan/app spec from the planner handoff.
- Check
appSpec.planAudit.checksbefore editing; treat blocked/failed checks as gates, not suggestions. - If
questionsNeededis true, ask the user before generating. - Apply
appSpec.designSystemfor visual tone, density, palette intent, touch layout rules, component rules, accessibility, and anti-patterns. - Apply
appSpec.blocksas reusable micro-template guidance. Selected block docs are references to adapt to the current entity/design system, not generic code to paste blindly. - If
appSpec.auth.requestedis true, implement the local/mock auth shape first and keep any named provider behind the auth seam. - Load only the references listed in the app spec.
- If the template is
generic-app, use the selected archetype reference to shape screens and entities instead of loading unrelated mobile templates. - Generate touch-first screens and local state.
- Validate navigation, touch targets, and state coverage.
- Run
buildable reviewfrom the selected app workspace when the CLI is available.
Build Order
- Create typed entities and local sample data.
- Build the first mobile screen around the main daily workflow.
- Add navigation only when the screen graph requires it.
- Add empty, completed, validation, and confirmation states as appropriate.
- Review against the selected mobile quality rubric.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 57 lines · 58 tokens per session scan A 581df462495c
buildable-mobile-builder is a skill published in the GitHub repository suntay44/buildable-plugin-skills (53 stars, last pushed 13d ago), licensed MIT. It adds 58 tokens to every session and 565 once invoked, about $0.0003 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 skills, from other repositories
agent-spec-mobile-react-native
Agent skill for spec-mobile-react-native - invoke with $agent-spec-mobile-react-native.
expo-native-ui
Framework (OSS). Build beautiful, native-feeling Expo screens. Covers Apple HIG styling, semantic colors, native controls, SF Symbols, media, animations, visual effects, gradients, storage, and responsive layout. For routing and navigation, use the expo-router skill.
expo-web-to-native
Framework (OSS). Migrate an existing web React app to a native iOS/Android app with Expo. Use when the user wants to turn a website into a mobile app, port a Next.js/Vite/CRA React codebase to React Native, reuse web code on native incrementally, or asks how web idioms (the DOM, CSS, React Router, localStorage…
truesheet-usage
Consumer-side guide for integrating @lodev09/react-native-true-sheet into a React Native app. Use this skill whenever the user wants to add, configure, control, or debug a bottom sheet using TrueSheet — including ref-based sheets, named global sheets, web support with TrueSheetProvider/useTrueSheet, React Navigation…
building-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
use-dom
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.