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 skills/nylo-core/claude-code/mobile-designnpx skills add nylo-core/claude-code --skill mobile-designgit clone --depth 1 https://github.com/nylo-core/claude-codeWhat 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.00056 | $0.03549 |
| Opus 5 | $0.00028 | $0.01775 |
| Sonnet 5 | $0.00011 | $0.00710 |
| Haiku 4.5 | $0.00006 | $0.00355 |
Grade A, and why
mobile-design 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill guides creation of distinctive, production-grade Flutter mobile interfaces for iOS and Android phones. Implement real working code with exceptional attention to platform conventions and creative choices. Target phones ONLY - no tablets.
The user provides mobile requirements: a screen, feature, or complete app to build. They may include context about platform preference, purpose, audience, or technical constraints.
Design Philosophy
Before coding, understand the context and commit FULLY to a platform-aware aesthetic direction. Timid design produces forgettable apps.
- Existing project first: Search the codebase for existing themes, colors, typography, and design patterns. New screens should feel like they belong to the same app. Consistency with established project aesthetics takes priority over introducing new styles.
- Platform: iOS, Android, or adaptive (both). Each has distinct conventions that users expect.
- Purpose: What problem does this interface solve? Who uses it one-handed on the go? What emotional state are they in?
- Tone: If no existing aesthetic exists, commit boldly to a direction:
- Refined luxury (restrained palette, generous whitespace, elegant typography)
- Playful casual (rounded shapes, bright colors, bouncy motion)
- Bold graphic (high contrast, strong typography, decisive color blocking)
- Organic soft (natural colors, fluid shapes, gentle gradients)
- Utilitarian functional (dense information, minimal decoration, maximum efficiency)
- Editorial magazine (dramatic type scale, asymmetric layouts, striking imagery)
- Dark moody (deep backgrounds, accent lighting, atmospheric depth)
- Vibrant energetic (saturated colors, dynamic composition, lively motion)
- The Unforgettable Element: What single thing will make users remember this screen? Every great interface has a signature moment - a striking header, a delightful transition, an unexpected color choice, a perfectly weighted animation. Identify yours before coding.
CRITICAL: Respect the existing project's design system first, then platform conventions, while expressing creativity within them. Generic Flutter defaults are unacceptable. Platform-inappropriate patterns are equally unacceptable. Ignoring established project patterns creates visual inconsistency.
Execution Principle: Complexity should match the aesthetic vision. A maximalist design warrants elaborate gradients, layered elements, and rich animation. A minimalist design requires restraint - every element must earn its place through precision and purpose. Don't apply maximalist techniques to minimal concepts or vice versa.
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.
- 2d ago First seen · 317 lines · 56 tokens per session scan A 5f726c072337
mobile-design is a skill published in the GitHub repository nylo-core/claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 3,549 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-31.
Other skills, from other repositories
at_client_skills-sdk
Use this skill when a developer is building a Dart or Flutter app that depends on atclient or atclientflutter from pub.dev, stores or shares data via the Atsign Protocol, needs onboarding (CRAM new-atsign, atKeys file, keychain, APKAM) or APKAM enrollment, or asks about AtCollection , CItem , Query , sub-collections…
flutter-pre-caching
Use when preloading fonts, asset/network images, Lottie/Rive animations, local JSON/config, warming initial API data, or optimizing Flutter Web startup.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
bloc
Use when creating a Cubit or Bloc, modeling state with sealed classes or status enums, wiring BlocBuilder/BlocListener/BlocProvider, writing bloc tests, or choosing between Cubit and Bloc.
firebase-auth
Use when setting up auth, managing auth state, implementing email/password or social sign-in, handling auth errors, or managing users.
dart-3-updates
Use when writing switch statements, refactoring if-else chains, creating data classes, choosing records vs classes, destructuring values, or modernizing pre-Dart-3 code.