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 instructions/hatefsystems/search-engine-core/env-configgit clone --depth 1 https://github.com/hatefsystems/search-engine-coreWhat 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.00347 | $0.00347 |
| Opus 5 | $0.00173 | $0.00173 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
search-engine-core env-config.instructions.md 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.
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.
- 2d ago First seen · 49 lines · 347 tokens per session scan A 803e6508ca28
search-engine-core env-config.instructions.md is an instructions file published in the GitHub repository hatefsystems/search-engine-core (5 stars, last pushed 28d ago), licensed Apache-2.0. It adds 347 tokens to every session, about $0.0017 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 instructions, from other repositories
Xapiand AGENTS.md
Instructions for Kronuz/Xapiand, covering agents.md — working in the xapiand codebase, first, the big split: own code vs. vendored, where things live, build & toggles and verifying changes end-to-end (the docs are a test suite).
electron CLAUDE.md
Instructions for electron/electron, covering electron development guide, running nodemodules binaries, project overview, directory structure and build tools setup.
electron copilot-instructions.md
Instructions for electron/electron, covering copilot instructions for electron, build system, linting, running a single test and example: npm run test -- -g "ipc".
compiler-explorer AGENTS.md
Instructions for compiler-explorer/compiler-explorer, covering agents.md, build & test commands, important workflow requirements, style guidelines and architecture guidelines.
weaviate CLAUDE.md
Claude Code instructions for weaviate/weaviate, covering claude.md, no bug is ever out of scope, build & run, build the binary (cgoenabled=0, static linking) and build debug binary (with delve support).
compiler-explorer copilot-instructions.md
Instructions for compiler-explorer/compiler-explorer: For each answer to the user, evaluate your level of confidence in the correctness of the answer on a scale from 1 to 10, where 1 is very uncertain and 10 is absolutely certain. If your confidence level is below 8, state so and suggest ways to verify the answer.