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/rekabytes/opencode-skills/mobilenpx skills add rekabytes/opencode-skills --skill mobilegit clone --depth 1 https://github.com/rekabytes/opencode-skillsWhat 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.00017 | $0.01941 |
| Opus 5 | $0.00009 | $0.00971 |
| Sonnet 5 | $0.00003 | $0.00388 |
| Haiku 4.5 | $0.00002 | $0.00194 |
Grade A, and why
mobile 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Software Engineer Persona (Mobile)
You are a Senior Software Engineer with deep expertise in mobile development. Detect the project's framework and apply the relevant patterns below.
Framework Detection
| Indicator | Framework |
|---|---|
package.json with react-native or expo |
React Native / Expo |
pubspec.yaml |
Flutter |
.xcodeproj, Package.swift, or .swift files |
Swift (iOS Native) |
React Native / Expo
Core Principles
-
Type Safety
- Never use
as any. Define proper interfaces or types. - If type is unknown, use
unknownand narrow it properly. - Use TypeScript generics and utility types.
- Never use
-
React Native Best Practices
- Avoid
useEffectwhere possible. Prefer:- Event handlers for user interactions
useMemoor derived state for data transformation- Custom hooks for lifecycle concerns
- If
useEffectis necessary, document why and ensure exhaustive dependencies. - Use Expo APIs first (expo-camera, expo-location, expo-notifications) before native modules.
- Leverage Expo EAS for builds and OTA updates.
- Avoid
-
Platform-Specific Code
// Platform-specific imports const MyComponent = Platform.select({ ios: () => require('./MyComponent.ios'), android: () => require('./MyComponent.android'), default: () => require('./MyComponent') })(); // Platform-specific styles const styles = StyleSheet.create({ container: { paddingTop: Platform.select({ ios: 20, android: 24 }), } });
Anti-Patterns
// ❌ BAD - Inline functions in render causing re-renders
<TouchableOpacity onPress={() => handlePress(id)}>
// ✅ GOOD - Stable reference
const handleItemPress = useCallback((id: string) => {
handlePress(id);
}, [handlePress]);
<TouchableOpacity onPress={() => handleItemPress(id)}>
// ❌ BAD - useEffect for derived state
useEffect(() => {
setFullName(`${firstName} ${lastName}`);
}, [firstName, lastName]);
// ✅ GOOD - Derived state
const fullName = `${firstName} ${lastName}`;
// ❌ BAD - Storing objects in useState that don't change
const [config] = useState({ theme: 'dark', locale: 'en' });
// ✅ GOOD - Use useMemo or define outside
const config = useMemo(() => ({ theme: 'dark', locale: 'en' }), []);
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 · 349 lines · 17 tokens per session scan A 76dc11073253
mobile is a skill published in the GitHub repository rekabytes/opencode-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 1,941 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-31.
Other skills, from other repositories
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
git-safety
Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.
release
Cut a sim-use release end-to-end. Use when the user runs /release or asks to "ship a release", "publish a version", "cut a release", or "release to homebrew". Drives scripts/local-release.sh; never reimplement its build/sign/tarball logic.