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 agents-inc/skills --skill mobile-ui-components-react-native-papergit clone --depth 1 https://github.com/agents-inc/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/agents-inc/skills/mobile-ui-components-react-native-paper)<a href="https://agentmods.dev/skills/agents-inc/skills/mobile-ui-components-react-native-paper"><img src="https://agentmods.dev/badge/skills/agents-inc/skills/mobile-ui-components-react-native-paper.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.00041 | $0.03574 |
| Opus 5 | $0.00020 | $0.01787 |
| Sonnet 5 | $0.00008 | $0.00715 |
| Haiku 4.5 | $0.00004 | $0.00357 |
Grade A, and why
mobile-ui-components-react-native-paper 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 4d 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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Native Paper Patterns
Quick Guide: React Native Paper v5+ provides Material Design 3 (Material You) components for React Native. Wrap your app in
PaperProvider(MD3 is the default). UseuseTheme()to access colors/fonts. Wrap Dialogs inPortal. Use the babel plugin for production bundle optimization. For BottomNavigation with React Navigation, useBottomNavigation.Baras a customtabBar(the oldcreateMaterialBottomTabNavigatoris deprecated). On Android 12+, useexpo-material3-themefor system dynamic colors.
<critical_requirements>
CRITICAL: Before Using This Skill
All code must follow project conventions in CLAUDE.md (kebab-case, named exports, import ordering,
import type, named constants)
(You MUST wrap your app root in PaperProvider - all Paper components require the provider context to function)
(You MUST wrap Dialog, Menu, and similar overlay components in Portal - without it they render inline instead of above other content)
(You MUST use useTheme() to access theme colors and fonts in components - never hardcode Material Design color values)
(You MUST add react-native-paper/babel to production plugins for bundle optimization - without it the entire library is included)
</critical_requirements>
Auto-detection: React Native Paper, react-native-paper, PaperProvider, MD3LightTheme, MD3DarkTheme, useTheme, Portal, FAB, Appbar, BottomNavigation, SegmentedButtons, configureFonts, adaptNavigationTheme, Card, Dialog, Snackbar, TextInput, Button mode, Surface, Chip, Searchbar, ActivityIndicator, Banner, Divider, ProgressBar, Switch, RadioButton, Checkbox, DataTable, Tooltip, Badge, Menu, Drawer.Item
When to use:
- Setting up PaperProvider with custom MD3 themes (light, dark, dynamic color)
- Using Paper components (Button, Card, TextInput, FAB, Appbar, Dialog, Snackbar, SegmentedButtons)
- Integrating Paper's BottomNavigation.Bar with React Navigation bottom tabs
- Configuring custom fonts with
configureFontsfor MD3 typography - Implementing Android 12+ dynamic color theming
- Bridging Paper and React Navigation themes with
adaptNavigationTheme
What ships with it
5 files 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.
- 4d ago First seen · 358 lines · 41 tokens per session scan A 5d6a99e047d9
mobile-ui-components-react-native-paper is a skill published in the GitHub repository agents-inc/skills (24 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 3,574 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
platform-conventions
Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use responsive-design; for matching competitor patterns use jakobs-law (interaction-design).
design-review
Use when adding or restyling a Facet UI component, or before merging a UI PR — walks the component against DESIGN.md (tokens, states, a11y, contrast, responsive) so the design system is matched, not just remembered. The judgment check verify.sh can't grep.
mobile-design
Guidance for designing and building mobile app interfaces on iOS and Android, including React Native and Flutter projects. Covers touch interaction, on-device performance, platform conventions, navigation, and offline behavior, and emphasizes reasoning about constraints over copying fixed values. Use it when creating…
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
conversational-ux
Design voice and conversational interfaces — dialog flows, error recovery, and persona. Use when the interface speaks and listens rather than being tapped. For graphical input collection, use form-design.
design-debt-audit
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use design-token-audit (designer-toolkit); for WCAG gaps use accessibility-audit (design-systems).