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/contentstack/contentstack-agent-skills/19-launch-sync-environment-variables-from-env-examplegit clone --depth 1 https://github.com/contentstack/contentstack-agent-skillsWhat 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.00984 | $0.00984 |
| Opus 5 | $0.00492 | $0.00492 |
| Sonnet 5 | $0.00197 | $0.00197 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
19-launch-sync-environment-variables-from-env-example 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Launch environment variables from .env.example
Description
Fetch environment variables from a Contentstack Launch project, compare them with a local .env.example file, and patch the target environment to add any missing keys.
When to Use
Use when a Launch environment must match the keys defined in a local .env.example file.
Use to audit missing environment variables before a deployment.
Use to add missing variable names to a Launch environment without manually editing config.
User Problem
A Launch environment can drift from the variables expected by a frontend project. This skill checks the environment against .env.example and updates Launch when keys are missing.
Success Criteria
All keys present in .env.example exist in the target Launch environment.
Missing keys are added through the Launch Projects/Environments API.
The script reports what was missing and what was updated.
No secrets are printed in logs.
Expected Inputs
- Launch project UID
- Launch environment UID
- Path to local
.env.examplefile - Launch API credentials or authenticated context
- Optional: dry-run flag
Expected Outputs
- List of keys found in
.env.example - List of keys already present in Launch
- List of missing keys that were patched
- Summary of API calls made
- Exit code indicating success or failure
Example User Requests
- Generate a Node.js script that syncs Launch environment variables from
.env.example. - Compare my Launch environment variables with
.env.exampleand add any missing keys. - Write a script to patch missing Launch environment variables for project abc123 and environment dev456.
Workflow Summary
Read and parse the local .env.example file.
Fetch the target Launch environment and its current variables.
Compare keys from the file against keys in Launch.
Build a minimal patch payload containing only missing keys.
Call PATCH /projects/{project_uid}/environments/{environment_uid}.
Report the changes and stop without exposing values.
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 · 131 lines · 984 tokens per session scan A 2025590e4bd3
19-launch-sync-environment-variables-from-env-example is a cursor rule published in the GitHub repository contentstack/contentstack-agent-skills (5 stars, last pushed 15d ago), licensed MIT. It adds 984 tokens to every session, about $0.0049 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.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.