env-management

A set of rules for handling environment variables and secrets in a web application. Environment variables are configuration values kept outside the source code, while secrets include passwords, API keys, and database credentials.

In plain words
What is it for?
Use it to name and classify environment variables, keep payment, database, and service keys on the server, structure local configuration, and validate missing values.
Why use it?
It reduces the risk of exposing server-only credentials in browser code. It also defines which public values may be sent to the client and how required values should be checked at startup.

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/vibestackdev/vibe-stack/env-management
Clone the repo
git clone --depth 1 https://github.com/vibestackdev/vibe-stack

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 490 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00490
Opus 5 $0.00000 $0.00245
Sonnet 5 $0.00000 $0.00098
Haiku 4.5 $0.00000 $0.00049

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

Security

Grade A, and why

env-management 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 yesterday.

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/env-management.mdc · 67 lines

What it actually says

Environment Variable Management

Classification Rules

Prefix Visibility Use For
NEXT_PUBLIC_ Client + Server Non-sensitive public values (Supabase URL, Stripe publishable key)
No prefix Server Only ALL secrets (API keys, webhook secrets, database URLs)

NEVER Expose These to the Client

STRIPE_SECRET_KEY         → Server only (NEVER NEXT_PUBLIC_)
STRIPE_WEBHOOK_SECRET     → Server only
SUPABASE_SERVICE_ROLE_KEY → Server only (admin bypass key)
RESEND_API_KEY            → Server only
DATABASE_URL              → Server only

Safe for Client

NEXT_PUBLIC_SUPABASE_URL           → Public Supabase endpoint
NEXT_PUBLIC_SUPABASE_ANON_KEY      → Rate-limited client key (RLS protects data)
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY → Stripe public key (payment form only)
NEXT_PUBLIC_APP_URL                → Your app's URL

Validation Pattern

Use src/lib/env.ts to validate at startup:

function getEnvVar(key: string, required = true): string {
  const value = process.env[key]
  if (!value && required) {
    throw new Error(`❌ Missing required env var: ${key}`)
  }
  return value ?? ''
}

.env.local Structure

# Supabase (required)
NEXT_PUBLIC_SUPABASE_URL=https://your-project.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=eyJ...

# Stripe (optional in dev)
STRIPE_SECRET_KEY=sk_test_...
STRIPE_WEBHOOK_SECRET=whsec_...
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=pk_test_...

# Email (optional in dev)
RESEND_API_KEY=re_...

# App
NEXT_PUBLIC_APP_URL=http://localhost:3000

Anti-Patterns

  • NEVER commit .env.local — it's in .gitignore
  • NEVER use process.env.X directly in components — use the centralized env config
  • NEVER hardcode API keys or secrets in source code
  • NEVER use NEXT_PUBLIC_ for write-access API keys
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. yesterday First seen · 67 lines · 0 tokens per session scan A c2ad01718d76

Subscribe to this mod's changes

env-management is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 490 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.