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/blockmatic/basilicWrote 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/blockmatic/basilic/env-files)<a href="https://agentmods.dev/rules/blockmatic/basilic/env-files"><img src="https://agentmods.dev/badge/rules/blockmatic/basilic/env-files/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/blockmatic/basilic/env-files"><img src="https://agentmods.dev/badge/rules/blockmatic/basilic/env-files.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.00000 | $0.00820 |
| Opus 5.5 | $0.00000 | $0.00328 |
| Sonnet 5.5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
env-files 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source of truth
- Runtime vars: each app’s
createEnvinlib/env.tsorsrc/lib/env.ts(t3-oss + Zod). Adding/removing a var requires updating that schema and the committed template(s) for that app. - Do not document env vars only in README without a template line.
Secrets and commits
- Never put real API keys, tokens, or production secrets in committed
.env.<qualifier>.exampletemplates, nor in.env.development,.env.staging, or.env.production. Use obvious placeholders (sk-ant-xxx,your_dynamic_environment_id). .env,.env.local, and secret-bearing.env.teststay gitignored per app; ship.env.test.examplewhere tests need a template.
Naming (templates) — pattern .env.<qualifier>.example
- Canonical glob:
**/.env.*.example(Cursor:@**/.env.*.example). Filenames must be.env.+ one qualifier +.example(e.g.defaults,local,test). Do not add.env.sample,.env-example, or bare.env.example. pnpm setup/pnpm setup:envcopies each template to its dest when the dest is missing (never overwrites). Mapping:.env.defaults.example→.env;.env.<qualifier>.example→.env.<qualifier>.- Fastify API (
apps/api):.env.defaults.example(copy to.env);.env.test.example→.env.test. - Next.js (
apps/web,apps/mathler):.env.local.example(copy to.env.local); committed.env.development/.env.staging/.env.productiononly for non-sensitive defaults (NEXT_PUBLIC_*, etc.). - Expo (
apps/mobile):.env.defaults.examplewithEXPO_PUBLIC_*. - Docu: committed
.env.development; optional.env.defaults.examplealigned withlib/env.ts. - Legacy:
.env.schemamay remain; updateblock-secret-files/ gitleaks when renaming templates.
Next.js section order (web + mathler)
Use the same header order in .env.local.example and committed .env.*:
- Short header (what is committed vs local-only).
- Client /
NEXT_PUBLIC_*(API URL, auth, logging, legal). - Server-only / local secrets (
JWT_SECRET, etc.) — template only where applicable. - E2E / Playwright (
PLAYWRIGHT_APP_URL,PLAYWRIGHT_API_URLon web; unify mathler on the same names; avoid duplicateBASE_URL/PLAYWRIGHT_TEST_BASE_URLwithout documented precedence). - Optional integrations (Sentry, …).
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 Changed · +1 lines · -13 tokens per session fb5c1722669f
- 1mo ago First seen · 49 lines · 13 tokens per session scan A 1443846f2954
env-files is a cursor rule published in the GitHub repository blockmatic/basilic (90 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 820 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-30.
Other cursor rules, from other repositories
hatch3r-typescript-patterns
TypeScript and JavaScript typing mechanics — satisfies over as, discriminated unions, branded types, strict utility types, barrel exports, and import ordering.
typescript-coding-standards
Production TypeScript coding standards.
testing-standards-typescript
When writing tests for typescript.
typescript-error-handling
Error handling patterns for TypeScript with Sentry.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.