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/hatefsystems/search-engine-coreWrote 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/hatefsystems/search-engine-core/env-config)<a href="https://agentmods.dev/rules/hatefsystems/search-engine-core/env-config"><img src="https://agentmods.dev/badge/rules/hatefsystems/search-engine-core/env-config/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/hatefsystems/search-engine-core/env-config"><img src="https://agentmods.dev/badge/rules/hatefsystems/search-engine-core/env-config.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.00010 | $0.00352 |
| Opus 5.5 | $0.00004 | $0.00141 |
| Sonnet 5.5 | $0.00002 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
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 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
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
.envwith credentials; use Docker secrets in production.
Configuration Priority
- Docker environment (highest)
.envfile (Docker Compose fallback)- 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;
}
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 · 50 lines · 10 tokens per session scan A 8a8c62822bba
env-config is a cursor rule published in the GitHub repository hatefsystems/search-engine-core (5 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 352 once invoked, about $0.0000 per session on Opus 5.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
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
hack
Hack is local-first. This project uses hack for local runtime orchestration (compose + DNS/TLS + logs + sessions). Prefer hack when shell access is available. Use MCP only when shell access is unavailable.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
container-rightsizer
Rightsizes container CPU and memory requests and limits using real usage data. Reduces requested resources without hitting OOMKills or CPU throttling.