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 rules/yosefhayim/launch-store/providersgit clone --depth 1 https://github.com/YosefHayim/launch-storeWhat 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.00000 | $0.00163 |
| Opus 5 | $0.00000 | $0.00081 |
| Sonnet 5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
providers 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.
What it actually says
Adding a backend = implement one of the five interfaces from src/core/types/providers.ts as a named object and register it in src/providers/index.ts, which wires into src/core/services/registry.ts.
- The pipeline resolves a provider by its
name(the value users put inlaunch.config.ts), so you never editsrc/core/build/pipeline.tsto add a backend. - Lazy-load heavy / optional SDKs (AWS, the native keyring) through
requireOptionalinsrc/core/services/optionalDep.ts, so a missing package becomes an actionable install hint instead of a stack trace.
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 · 11 lines · 0 tokens per session scan A af9e1d42280d
providers is a cursor rule published in the GitHub repository YosefHayim/launch-store (9 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 163 tokens. 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 cursor rules, from other repositories
compose-coroutines
Compose scroll/coroutine patterns — prevent programmatic scroll from being mistaken for user scroll, cancellation-safe flag resets.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
shared-module
KMP shared module constraints — no platform imports in domain/, expect/actual conventions, pure Kotlin business logic.
utilities
Lodash 和 Moment.js 工具庫使用規範.
android-gradle-build-logic
Shape Android build logic with Gradle, version catalogs, plugins, convention patterns, and toolchain compatibility.
android-kotlin-core
Use Kotlin idioms safely in Android apps, including nullability, data classes, sealed types, extension functions, and collection pipelines.