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 SummerRiversound/expo-launchpad --skill expo-launchpad-designgit clone --depth 1 https://github.com/SummerRiversound/expo-launchpadWrote 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/summerriversound/expo-launchpad/expo-launchpad-design)<a href="https://agentmods.dev/skills/summerriversound/expo-launchpad/expo-launchpad-design"><img src="https://agentmods.dev/badge/skills/summerriversound/expo-launchpad/expo-launchpad-design/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/summerriversound/expo-launchpad/expo-launchpad-design"><img src="https://agentmods.dev/badge/skills/summerriversound/expo-launchpad/expo-launchpad-design.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.00064 | $0.04026 |
| Opus 5.5 | $0.00026 | $0.01610 |
| Sonnet 5.5 | $0.00013 | $0.00805 |
| Haiku 4.5 | $0.00006 | $0.00403 |
Grade A, and why
expo-launchpad-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 1mo 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 — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
expo-launchpad-design
Phase A, step 3 of the expo-launchpad pipeline. Reads the latest PRD and config.md, then produces
a design document that specifies the ui/designTokens.ts constants, the visual/component concept,
and the asset plan (including app icon and splash intent). Advances the pipeline state to
contract.
All file schemas (config.md, state.md, pipeline-log.md) and the phase transition table are
defined in docs/harness-protocol.md — refer to that document as the single source of truth (§2
for state.md schema; §7 for the design → contract transition). Do not redefine schemas here.
Input
1. Read docs/harness/config.md
Extract:
| Key | Use |
|---|---|
kind |
app or game — drives which visual/component template and project-structure slot this skill fills |
engine |
skia — the only supported Phase A value, meaningful only when kind: game. The design spec below is renderer-agnostic (shapes/primitives + tokens) |
app_name |
Used in the splash screen and app-icon badge intent |
app_slug |
Used for asset directory naming conventions |
default_language |
The user's conversation language; write the design doc's prose and copy samples in it |
If config.md does not exist, abort with:
expo-launchpad-design: docs/harness/config.md not found — run the orchestrator to bootstrap first.
2. Read the latest PRD
Find the most recent file matching docs/harness/plans/*-prd.md (sort descending by filename,
take the first). If no PRD exists, abort with:
expo-launchpad-design: no PRD found in docs/harness/plans/ — run expo-launchpad-plan first.
Extract from the PRD, branching on kind:
kind: game — §1 Genre & Concept (genre, tone, target age), §2 Core Loop, §6 Win/Lose
Conditions (what UI states need distinct visual treatment), §9 Project Structure.
kind: app — §1 Purpose & Users (tone, target users), §2 Primary Journeys (screens to design),
§5 States (loading/empty/error per screen), §6 Navigation Map, §9 Project Structure.
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.
- 1mo ago First seen · 370 lines · 64 tokens per session scan A 955b5fb2868c
expo-launchpad-design is a skill published in the GitHub repository SummerRiversound/expo-launchpad (2 stars, last pushed 4d ago), licensed MIT. It adds 64 tokens to every session and 4,026 once invoked, about $0.0003 per session on Opus 5.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
mobile-developer
Expert in React Native, Expo, and cross-platform mobile development.
uniwind
Uniwind — Tailwind CSS v4 styling for React Native. Use when adding, building, or debugging components in a React Native project that uses Uniwind classNames. Covers setup, Metro config, global.css, theming, className props, accent- color props, platform/data/state/responsive variants, CSS variables, custom utilities…
compose-component-design
Use when designing or reviewing reusable Jetpack Compose component APIs with modifier parameters, root layout placement, caller-provided variable content, primitive content parameters, optional content, or boolean shape flags.
compose-multiplatform
Use when building one shared Compose UI in Kotlin across Android, iOS, and desktop — commonMain @Composables, expect/actual, source-set placement, native interop, multiplatform ViewModel/navigation/Koin. NOT a single-platform native build (that is kotlin-android / swift-ios), and NOT Dart/Flutter cross-platform UI…
react-native
Use when writing the JS/TS inside a React Native or Expo app — screens, Expo Router navigation, lists, Reanimated gestures, platform forks, offline state, native modules — or killing jank and render storms. NOT eas build/submit/OTA/config-plugin (that is expo), NOT a Dart app (that is flutter), NOT web React/DOM (that…
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.