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-resumegit 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-resume)<a href="https://agentmods.dev/skills/summerriversound/expo-launchpad/expo-launchpad-resume"><img src="https://agentmods.dev/badge/skills/summerriversound/expo-launchpad/expo-launchpad-resume/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-resume"><img src="https://agentmods.dev/badge/skills/summerriversound/expo-launchpad/expo-launchpad-resume.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.00039 | $0.01724 |
| Opus 5 | $0.00019 | $0.00862 |
| Sonnet 5 | $0.00008 | $0.00345 |
| Haiku 4.5 | $0.00004 | $0.00172 |
Grade A, and why
expo-launchpad-resume 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 11d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
expo-launchpad-resume
Resume handler for the expo-launchpad pipeline. Reads docs/harness/state.md, decides whether the
paused run is the Phase A terminal human-review gate or an ordinary pause, and either finalizes the
run as completed or restores status: running and re-enters the orchestrator's dispatch loop.
All file schemas (state.md, pipeline-log.md) and the state transition rules are defined in
docs/harness-protocol.md — refer to §2 (state.md schema) and §7 (Phase Transition Table,
including the Phase B seam note) as the single source of truth. Do not redefine schemas here.
docs/harness/ lives at the workspace root — the directory the pipeline was invoked from —
for the entire pipeline, never inside the generated <app_slug>/ project. This skill reads and
writes docs/harness/state.md and docs/harness/pipeline-log.md relative to the current working
directory (the invocation dir), the same convention used by every other phase skill.
Input
Read docs/harness/state.md. If it does not exist, abort with:
Nothing to resume — no state.md found. Run without --resume to start a new pipeline.
Extract per the schema in docs/harness-protocol.md §2: status, current_phase,
current_round, next_role, pause_reason, resume_attempts, checkpoint, created_at,
updated_at.
- If
status: running— printexpo-launchpad-resume: pipeline is already running (next_role: <next_role>). No resume needed.and exit. - If
status: completed— printexpo-launchpad-resume: pipeline is already completed. Nothing to resume.and exit. - If
statusis anything other thanpaused/running/completed, abort with:expo-launchpad-resume: unexpected status "<value>" in state.md — inspect docs/harness/state.md manually.
Otherwise (status: paused), continue below.
Which pause is this?
Per docs/harness-protocol.md §7, evaluator | PASS | paused (manual_action) unless auto_deploy
is the only transition in Phase A that pauses the pipeline for a human to approve finished
work — expo-launchpad-evaluator writes this exact combination on a PASS:
current_phase: evaluator, next_role: evaluator, pause_reason: manual_action. The other
pause_reason: manual_action writes in this pipeline from research's unresolved clone-avoidance
check, plan's unresolved clone signal, design's missing PRD, and contract's missing PRD/design doc
leave current_phase at that skill's own phase, never evaluator, so those cases never collide.
Generator's missing-prior-round-feedback abort is different: current_phase can be stale at
evaluator there (carried over from the prior FAIL write), so current_phase alone cannot be
trusted to tell that abort apart from the terminal case. The field that actually disambiguates is
next_role, which stays generator on this abort versus evaluator on the terminal PASS.
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.
- 11d ago First seen · 172 lines · 39 tokens per session scan A b6d133d497d4
expo-launchpad-resume is a skill published in the GitHub repository SummerRiversound/expo-launchpad (2 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,724 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-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…
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.
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…
react-native-expert
Expert in React Native, cross-platform mobile development, native modules, and performance optimization. Use when the user mentions mobile, JavaScript, TypeScript, cross platform, iOS, or Android, or when the task involves React Native Architecture, Component Types, Hooks Essentials, or Navigation.