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/diegomarino/awesomic-cursor-rules/environment-variablesgit clone --depth 1 https://github.com/diegomarino/awesomic-cursor-rulesWrote 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/diegomarino/awesomic-cursor-rules/environment-variables)<a href="https://agentmods.dev/rules/diegomarino/awesomic-cursor-rules/environment-variables"><img src="https://agentmods.dev/badge/rules/diegomarino/awesomic-cursor-rules/environment-variables.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00769 |
| Opus 5 | $0.00000 | $0.00385 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
environment-variables 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 4d 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.
Environment Variables Standards
File Structure
- Use descriptive section headers
- Include detailed comments for each variable
- Group related variables together
- Follow consistent naming conventions (by default use SCREAMING_SNAKE_CASE if none specified)
- Align comments vertically within each group for better readability
Required Environment Files
.env- Main development configuration (gitignored).env.example- Template with dummy values (committed).env.test- Test environment configuration (gitignored).env.production- Production settings (gitignored)
Optional but recommended:
.env.local- Local overrides, for developer-specific settings (gitignored)
Variable Categories
Environment Configuration
NODE_ENV:
description: Application environment setting
allowed_values: [development, production, test]
required: true
DEBUG:
description: Debug mode configuration
allowed_values: [true, false, trace, debug, info, warn, error]
default: false
Logging Configuration
LOG_ENABLED:
description: Enable/disable application logging
type: boolean
required: true
LOG_LEVEL:
description: Logging verbosity level
allowed_values: [error, warn, info, debug, trace]
default: info
LOG_FILE:
description: Main log file name
type: string
required: true
LOG_PATHS:
description: Logging path configuration
type: object
properties:
LATEST: string # Path for latest log file
HISTORY: string # Path pattern for historical logs
LOG_ROTATION:
description: Log rotation settings
type: object
properties:
MAX_SIZE: string # Size threshold for rotation
MAX_FILES: string # Retention period
Locale Settings
TIMEZONE:
description: Application timezone
type: string
required: true
example: UTC
LANGUAGE:
description: Default application locale
type: string
pattern: [a-z]{2}-[A-Z]{2}
required: true
example: en-US
Directory Configuration
DIRECTORIES:
description: Application directory structure
type: object
note: "Paths should be relative to project root"
properties:
OUTPUT: string # Output directory
TEMPLATES: string # Templates directory
STATIC: string # Static assets directory
DATA: string # Data files directory
LOGS: string # Logs directory
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.
- 4d ago First seen · 131 lines · 0 tokens per session scan A f07a0febfa47
environment-variables is a cursor rule published in the GitHub repository diegomarino/awesomic-cursor-rules (10 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 769 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.
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.