exec-secrets

exec-secrets is a cursor rule for Cursor from YosefHayim/launch-store. It costs 0 tokens per session (160 once invoked), scanned A, original, MIT.

Project rules for safely running child processes and handling credentials such as private keys and keystores.

In plain words
What is it for?
Use them when implementing code that starts other programs or reads credentials. They specify how processes must be launched and where secrets and non-secret references belong.
Why use it?
They reduce the risk of shell-injection problems, accidental secret exposure, and committing sensitive key material.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use them when implementing code that starts other programs or reads credentials. They specify how processes must be launched and where secrets and non-secret references belong.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/yosefhayim/launch-store/exec-secrets
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.

Clone the repo
git clone --depth 1 https://github.com/YosefHayim/launch-store

Made for: Cursor.

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

agentmods badge for exec-secrets

README.md
[![agentmods](https://agentmods.dev/badge/rules/yosefhayim/launch-store/exec-secrets/github.svg)](https://agentmods.dev/rules/yosefhayim/launch-store/exec-secrets)
Your own site
<a href="https://agentmods.dev/rules/yosefhayim/launch-store/exec-secrets"><img src="https://agentmods.dev/badge/rules/yosefhayim/launch-store/exec-secrets/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.

agentmods 80×15 button for exec-secrets

Your own site · 80×15
<a href="https://agentmods.dev/rules/yosefhayim/launch-store/exec-secrets"><img src="https://agentmods.dev/badge/rules/yosefhayim/launch-store/exec-secrets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 160 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00160
Opus 5.5 $0.00000 $0.00064
Sonnet 5.5 $0.00000 $0.00032
Haiku 4.5 $0.00000 $0.00016

Measured 1mo ago against content hash a60b59ef184d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

exec-secrets 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.

.cursor/rules/exec-secrets.mdc · 10 lines

What it actually says

All child processes go through src/core/services/exec.ts - run streams output, capture collects stdout - both with shell: false and an explicit argv array. Never build a shell string or call spawn / exec directly.

  • Secrets (.p8 / .p12 / keystore / private keys) live in the OS keychain via the secret store; ~/.launch holds non-secret paths and ids only. Don't log, write, or commit key material.
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. 1mo ago First seen · 10 lines · 0 tokens per session scan A a60b59ef184d

Subscribe to this mod's changes

exec-secrets 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 160 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.