env-config

Rules for reading application settings from environment variables with C++’s std::getenv and Docker Compose. They describe defaults, type conversion, container settings, and keeping secret values out of Git.

In plain words
What is it for?
Use them to configure SMTP, MongoDB, Redis, logging, and Browserless connections; parse Boolean and integer settings; set Compose defaults; and handle production secrets safely.
Why use it?
They provide one consistent way to configure an app across local development, Docker containers, and production without hard-coding credentials or writing a custom .env reader.

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/hatefsystems/search-engine-core/env-config
Clone the repo
git clone --depth 1 https://github.com/hatefsystems/search-engine-core

Made for: Cursor.

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 352 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.00010 $0.00352
Opus 5 $0.00005 $0.00176
Sonnet 5 $0.00002 $0.00070
Haiku 4.5 $0.00001 $0.00035

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

Security

Grade A, and why

env-config 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-config.mdc · 50 lines

What it actually says

Environment Variable Configuration

Use std::getenv() for configuration (works with Docker Compose and .env).

const char* host = std::getenv("SMTP_HOST");
config.smtpHost = host ? host : "smtp.gmail.com";
// Boolean: compare to "true", "1", "yes" (case-insensitive)
// Integer: std::stoi with try/catch and default
  • Do not create custom .env parser classes.
  • Containers: core, mongodb_test, redis, browserless.
  • Critical: LOG_LEVEL, MONGODB_URI, REDIS_URL, BROWSERLESS_URL.
  • Never commit .env with credentials; use Docker secrets in production.

Configuration Priority

  1. Docker environment (highest)
  2. .env file (Docker Compose fallback)
  3. Default values in code

Docker Compose Pattern

environment:
  - SMTP_HOST=${SMTP_HOST:-smtp.gmail.com}
  - SMTP_PORT=${SMTP_PORT:-587}
  - SMTP_USE_TLS=${SMTP_USE_TLS:-true}

Boolean/Integer Parsing

// Boolean: compare to "true", "1", "yes" (case-insensitive)
// Integer: std::stoi with try/catch and default
const char* port = std::getenv("SMTP_PORT");
try {
    config.smtpPort = port ? std::stoi(port) : 587;
} catch (const std::exception& e) {
    LOG_WARNING("Invalid SMTP_PORT, using default: 587");
    config.smtpPort = 587;
}
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 · 50 lines · 10 tokens per session scan A 8a8c62822bba

Subscribe to this mod's changes

env-config is a cursor rule published in the GitHub repository hatefsystems/search-engine-core (5 stars, last pushed 28d ago), licensed Apache-2.0. It adds 10 tokens to every session and 352 once invoked, about $0.0001 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.