launch

A set of always-on working rules for the launch CLI codebase, a Node.js and TypeScript command-line application for app-store work. It explains where code belongs, how changes should be tested, and which checks must pass.

In plain words
What is it for?
Use it when modifying launch commands, core logic, store backends, documentation, tests, or build processes in that repository.
Why use it?
It keeps contributions consistent and prevents misplaced files, undocumented command changes, missing tests, and accidental exposure of secrets.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/yosefhayim/launch-store/launch
Clone the repo
git clone --depth 1 https://github.com/YosefHayim/launch-store

Made for: Cursor.

Per session 313 This file is loaded in full into every session.
When invoked 313 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00313 $0.00313
Opus 5 $0.00156 $0.00156
Sonnet 5 $0.00063 $0.00063
Haiku 4.5 $0.00031 $0.00031

Measured 2d ago against content hash e482faf87a05, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

launch 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.

.cursor/rules/launch.mdc · 13 lines

What it actually says

You are working on launch-store (the launch CLI), not using it. The canonical working rules live in AGENTS.md and CLAUDE.md - read them first.

  • One Node ESM / TypeScript package. src/cli is thin Commander wiring, src/core is purpose-grouped domain code, src/providers are swappable backends, src/apple and src/google are store API mirrors, and src/testkit holds shared fakes/layers.
  • Do not create flat src/core/*.ts files. Put new core work under the owning purpose folder such as build/, config/, credentials/, release/, store/, services/, terminal/, or types/.
  • Before calling a change done, run pnpm typecheck && pnpm lint && pnpm lint:style && pnpm docs:check && pnpm test && pnpm build (the generated docs + these rules are gated).
  • Keep it KISS / YAGNI / DRY: extend the nearest sibling file rather than inventing a new file, util, or abstraction. Add a test (*.test.ts) beside any new logic.
  • Never log, write, or commit secrets; ~/.launch holds non-secret paths and ids only.
Changes

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.

  1. 2d ago First seen · 13 lines · 313 tokens per session scan A e482faf87a05

Subscribe to this mod's changes

launch is a cursor rule published in the GitHub repository YosefHayim/launch-store (9 stars, last pushed 5d ago), licensed MIT. It adds 313 tokens to every session, about $0.0016 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.