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 FouadMagdy01/RNCopilot --skill create-screengit clone --depth 1 https://github.com/FouadMagdy01/RNCopilotWrote 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/fouadmagdy01/rncopilot/create-screen)<a href="https://agentmods.dev/skills/fouadmagdy01/rncopilot/create-screen"><img src="https://agentmods.dev/badge/skills/fouadmagdy01/rncopilot/create-screen.svg" alt="Measured on agentmods" 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.00018 | $0.01286 |
| Opus 5 | $0.00009 | $0.00643 |
| Sonnet 5 | $0.00004 | $0.00257 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade A, and why
create-screen 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.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Screen / Tab
Add a new screen or tab following expo-router conventions and project patterns.
Gather Information
Ask the user for:
- Screen name (e.g., "products", "order-details", "profile")
- Type: tab screen, stack screen, or modal
- Location in routing:
- Tab:
app/(main)/(tabs)/<name>.tsx - Stack within main:
app/(main)/<name>.tsx - Auth screen:
app/(auth)/<name>.tsx
- Tab:
- Protected? Does it require authentication?
- Needs backing data? If yes, suggest running
/create-featurefirst
Steps
1. Create the Screen File
Screen files use lowercase with hyphens and default exports.
// app/(main)/(tabs)/<name>.tsx OR app/(main)/<name>.tsx
import { useTranslation } from 'react-i18next';
import { StyleSheet } from 'react-native-unistyles';
import { ScreenContainer } from '@/common/components/ScreenContainer';
import { Text } from '@/common/components/Text';
import { ErrorBoundary } from '@/common/components/ErrorBoundary';
export default function <Name>Screen() {
const { t } = useTranslation();
return (
<ScreenContainer scrollable padded>
<ErrorBoundary>
<Text variant="h1">{t('<name>.title')}</Text>
</ErrorBoundary>
</ScreenContainer>
);
}
const styles = StyleSheet.create((theme) => ({
// Add styles as needed
}));
If protected (requires auth):
import { useProtectedRoute } from '@/hooks/useProtectedRoute';
export default function <Name>Screen() {
useProtectedRoute(); // Redirects to /(auth)/login if not authenticated
const { t } = useTranslation();
// ... rest of screen
}
2. Register as Tab (if tab screen)
Edit app/(main)/(tabs)/_layout.tsx to add the new tab:
<Tabs.Screen
name="<name>"
options={{
title: t('tabs.<name>'),
tabBarIcon: ({ color, size }) => (
<Icon name="<icon-name>-outline" color={color} size={size} />
),
}}
/>
The Icon component uses Ionicons names. Choose an appropriate icon from the Ionicons set.
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 · 192 lines · 18 tokens per session scan A 7fa03098f327
create-screen is a skill published in the GitHub repository FouadMagdy01/RNCopilot (41 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 1,286 once invoked, about $0.0001 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
flutter-setup-localization
Add flutterlocalizations and intl dependencies, enable "generate true" in pubspec.yaml, and create an l10n.yaml configuration file. Use when initializing localization support for a new Flutter project.
asc-localize-metadata
Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.
asc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
ios-marketing-capture
Use when the user wants to automate capture of marketing screenshots for a SwiftUI iOS app across multiple locales, devices, or appearances. Covers full-screen shots, isolated element renders (carousel cards, widgets), and reproducible output naming. Triggers on marketing screenshots, locale screenshots, widget…
localization-l10n
Implement localization (l10n) best practices to adapt applications for specific regions, languages, and cultural preferences.
maui-localization-theming
Implement MAUI localization and theming. USE FOR: RESX/AppResources, runtime culture switching, RTL/FlowDirection, platform language metadata, AppThemeBinding, DynamicResource, light/dark/system themes, UserAppTheme. DO NOT USE FOR: general layout, accessibility audits, icon/splash assets.