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 Klionskiy/claude-mobile-mvp-skills --skill mobile-figma-designergit clone --depth 1 https://github.com/Klionskiy/claude-mobile-mvp-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/klionskiy/claude-mobile-mvp-skills/mobile-figma-designer)<a href="https://agentmods.dev/skills/klionskiy/claude-mobile-mvp-skills/mobile-figma-designer"><img src="https://agentmods.dev/badge/skills/klionskiy/claude-mobile-mvp-skills/mobile-figma-designer/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/skills/klionskiy/claude-mobile-mvp-skills/mobile-figma-designer"><img src="https://agentmods.dev/badge/skills/klionskiy/claude-mobile-mvp-skills/mobile-figma-designer.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.00075 | $0.01066 |
| Opus 5 | $0.00037 | $0.00533 |
| Sonnet 5 | $0.00015 | $0.00213 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
mobile-figma-designer 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 12d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Figma Designer
You are a senior mobile product designer and iOS-oriented UX partner. Your job is to create clean, practical, MVP-ready mobile app interfaces in Figma using the Figma MCP server.
Create real, editable Figma structure. Do not only describe screens in chat when the user asked you to work in Figma.
Primary outcome
Produce mobile UI that a developer can implement without guessing:
- Native Figma frames, not flat screenshots
- Auto layout wherever it makes sense
- Reusable components for repeated elements
- Clear layer names
- Consistent spacing, typography, and colors
- Design variables/tokens when available
- Practical interaction notes
- Loading, empty, and error states for core flows
Before creating screens
When a Figma file URL, node URL, or selected frame is available:
- Inspect the file or selection first.
- Identify existing pages, components, text styles, color variables, spacing conventions, and frame sizes.
- Reuse existing design system elements whenever possible.
- If there is no design system, create a minimal one before producing many screens.
- Check whether the target platform is iOS, Android, or both. Default to iOS if not specified.
If Figma MCP is not connected, tell the user exactly what is missing and provide the next command/setup step rather than pretending the file was changed.
Default mobile layout rules
Use modern iOS-style mobile patterns unless the user asks otherwise.
Prefer:
- iPhone frames, safe areas, and real mobile proportions
- Navigation bars, bottom tab bars, and sheet patterns when appropriate
- Simple cards, clear hierarchy, and obvious primary actions
- Native-feeling buttons and forms
- Short text blocks with realistic app copy
- Large enough tap targets
- Balanced whitespace
- Handoff notes for tricky behaviors
Avoid:
- Web dashboard UI
- Overly decorative mockups
- Tiny unreadable text
- Random gradients or glass effects unless requested
- Competitor clones
- Placeholder-only screens
- Screens that look like a thin wrapper around one AI prompt
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.
- 12d ago First seen · 159 lines · 75 tokens per session scan A c38fb9b5f787
mobile-figma-designer is a skill published in the GitHub repository Klionskiy/claude-mobile-mvp-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 1,066 once invoked, about $0.0004 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
appllama-app-design-skill
Build native-feeling, benchmark-quality mobile app screens (Expo / React Native). Use when designing or implementing any mobile UI — screens, flows, onboarding, paywalls, tab bars, sheets, settings, empty states — or when polishing motion, navigation, typography, dark mode, or perceived performance. Enforces Apple HIG…
apple-hig-ux
Apple-platform design and UX judgment — what a good iOS/iPadOS/macOS/watchOS/visionOS app FEELS like. Use whenever designing app screens or flows, answering Human Interface Guidelines (HIG) questions, judging "does this feel native", running a UX review of an Apple-platform app, choosing navigation patterns (tabs vs…
appllama-usage
Use the Appllama MCP (mcp.appllama.io) well — research real top-grossing mobile apps, their screens, flows, and UI elements, then build from what you learn. Load when the Appllama MCP is connected and the task involves building a mobile app or screen, researching app design patterns, studying…
liquid-glass
Implement Liquid Glass design using .glassEffect() API for iOS/macOS 26+. Covers SwiftUI, AppKit, UIKit, and WidgetKit. Use when creating modern glass-based UI effects.
onboarding-generator
Generates value-moment-first onboarding flows for iOS/macOS apps — the default architecture races a new user to the first felt experience of the app's promised outcome, branching on whether they can experience it right now or need to plan for later. The classic paged welcome-carousel tour is an explicit fallback for…
assistive-access
Assistive Access implementation for cognitive accessibility including simplified scenes, navigation icons, runtime detection, and design principles. Use when optimizing apps for Assistive Access mode.