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.
git clone --depth 1 https://github.com/YosefHayim/launch-storeWrote 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/rules/yosefhayim/launch-store/providers)<a href="https://agentmods.dev/rules/yosefhayim/launch-store/providers"><img src="https://agentmods.dev/badge/rules/yosefhayim/launch-store/providers/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/rules/yosefhayim/launch-store/providers"><img src="https://agentmods.dev/badge/rules/yosefhayim/launch-store/providers.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.00000 | $0.00163 |
| Opus 5.5 | $0.00000 | $0.00065 |
| Sonnet 5.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 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.
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.
- 1mo 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 yesterday), 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
appstore-ppp-pricing
Bulk-set App Store in-app purchase and subscription prices across 175+ countries by purchasing power parity (PPP) with the appstore-ppp-prices CLI. Use for regional App Store pricing, price localization, bulk price updates, or making an app cheaper in emerging markets.
api-patterns
Rules for calling APIs, which are services that let an app request or send data, including how to define endpoints and handle errors.
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI, config schema and CLI packaging sync before lint, final checks, the comment on an issue a merge closes and the cleanup after the merge.
hatch3r-api-design
REST, GraphQL, and gRPC contract patterns covering versioning, auth, CORS, pagination, webhooks, rate limiting, and security headers.
hatch3r-scalability
CQ6 Scalability Quality measurement rule — stateless-handler ratio, back-pressure pattern adoption, idempotency-key adoption on POST/PUT/PATCH, queue offloading for >1s ops, pool sizing per concurrency profile.
adr-004
Cursor rule "adr-004" from actual-software/actual-cli, covering adopt secure secrets management in ci/cd pipeline and policies.