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 MartinPuli/createAnApp --skill app-launch-operatorgit clone --depth 1 https://github.com/MartinPuli/createAnAppWrote 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/martinpuli/createanapp/app-launch-operator)<a href="https://agentmods.dev/skills/martinpuli/createanapp/app-launch-operator"><img src="https://agentmods.dev/badge/skills/martinpuli/createanapp/app-launch-operator/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/martinpuli/createanapp/app-launch-operator"><img src="https://agentmods.dev/badge/skills/martinpuli/createanapp/app-launch-operator.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.00076 | $0.00760 |
| Opus 5.5 | $0.00030 | $0.00304 |
| Sonnet 5.5 | $0.00015 | $0.00152 |
| Haiku 4.5 | $0.00008 | $0.00076 |
Grade A, and why
app-launch-operator 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Launch Operator
Turn approval into a controlled distribution experiment. Do not equate downloads, one purchase, or App Store approval with product-market fit.
Verify launch prerequisites
Confirm storefront availability/release state, working commerce, support coverage, public privacy/terms/support pages, product analytics source, campaign attribution, crash/incident response, rollback path, budget authorization, and policy-safe creative provenance.
Do not install tracking merely to optimize ads without reopening $app-compliance-auditor and updating disclosures/consent/labels.
Choose a beachhead
Define one target segment, painful job, purchase moment, territory, promise, proof, and primary channel. Select channels by buyer behavior rather than fashion. Favor high-intent search, niche communities, tutorials, creators, partners, and Apple product pages that match the job.
Build truthful assets
Create a hook, real app demonstration, proof, objection answer, and CTA. Use captured release UI rather than AI-generated fake screens. AI may assist production, but never fabricate a customer, testimonial, review, creator endorsement, expert, revenue, result, or scarcity. Preserve source/license/AI/approval records.
Read references/creative-and-presence.md when establishing the domain, support email, social profiles, short-form videos, or AI-assisted creative pipeline.
Instrument attribution
Use App Store campaign links and Custom Product Pages where useful. Define naming conventions for channel, audience, creative, promise, and date. Use App Analytics/Sales/Subscriptions as the source of truth when no declared first-party telemetry exists.
Measure the funnel:
- impression or qualified reach;
- product-page view;
- download;
- first launch;
- core-job activation;
- paywall view;
- trial/purchase;
- renewal/retention;
- refund/cancellation/support burden;
- proceeds and contribution after fees/spend.
Use App Store Connect Analytics definitions and account for usage-data opt-in/privacy thresholds. Compare channels on retained paying cohorts and contribution, not download volume alone.
What ships with it
3 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.
- 1mo ago First seen · 62 lines · 76 tokens per session scan A 1b72f760db2d
app-launch-operator is a skill published in the GitHub repository MartinPuli/createAnApp (14 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 760 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-30.
Other skills, from other repositories
figma-a11y-annotations
Rules for generating accessibility annotations on iOS/iPadOS mobile designs in Figma. Enforces a bare-minimum annotation discipline, an iOS vocabulary instead of web ARIA terms, and exact grammar for names, control types, page titles, values, hints, headings, groups, and reading order. Never annotates visible text as…
iOS SwiftUI Accessibility
Enforces WCAG 2.2 accessible coding patterns when writing SwiftUI — labels, traits, Dynamic Type, contrast, touch targets, focus management, orientation, and more. Based on the ios-swiftui-accessibility-techniques project with 41 static analysis rules across 24 WCAG criteria.
workflow-audit
Systematic UI workflow auditing for SwiftUI applications. Discovers entry points, traces user flows, detects dead ends and broken promises, audits data wiring, evaluates from user perspective. Triggers: "workflow audit", "audit flows", "find dead ends", "check navigation".
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…
swift-expert
Expert-level Swift development for iOS, macOS with SwiftUI, Combine, and modern Swift 5.9+. Use when the user mentions iOS, macOS, SwiftUI, Combine, async await, or Apple platforms, or when the task involves Modern Swift Features, Basics and Optionals, Functions and Closures, or Structs and Classes.
ios-expert
Expert in iOS development with SwiftUI, UIKit, Combine, and Apple ecosystem integration. Use when the user mentions mobile, Swift, SwiftUI, UIKit, Apple platforms, or Xcode, or when the task involves iOS App Architecture, SwiftUI Fundamentals, UIKit Essentials, or Combine Framework.