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/seeincodes/skyfi-mcp/env-files-read-onlygit clone --depth 1 https://github.com/seeincodes/skyfi-mcpWrote 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/seeincodes/skyfi-mcp/env-files-read-only)<a href="https://agentmods.dev/rules/seeincodes/skyfi-mcp/env-files-read-only"><img src="https://agentmods.dev/badge/rules/seeincodes/skyfi-mcp/env-files-read-only.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.1 | $0.00302 | $0.00302 |
| Opus 5 | $0.00151 | $0.00151 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
env-files-read-only 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.
What it actually says
Environment File Protection
Rules
- Never modify .env files without explicit user confirmation
- Never commit .env files to git — they are in .gitignore
- Never display API key values in output, logs, or error messages
- Never hardcode secrets in source code — always reference env vars
- Never log environment variables at runtime (even at DEBUG level)
Required Environment Variables
SKYFI_API_KEY= # SkyFi platform API key
SKYFI_API_BASE_URL= # SkyFi API base URL
SKYFI_API_VERSION= # Pinned API version
SKYFI_SIMULATE= # Simulation mode toggle
PORT= # HTTP server port
RATE_LIMIT_PER_MIN= # Per-key rate limit
LOG_LEVEL= # Logging level
Adding New Environment Variables
- Add the variable to
.env(local, not committed) - Add the variable with empty value to
.env.example(committed) - Add the variable to
docs/TECH_STACK.mdEnvironment Variables section - Add validation in the config loader (fail fast on missing required vars)
- Document the variable's purpose and default value
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 · 36 lines · 302 tokens per session scan A f7cc34df4cca
env-files-read-only is a cursor rule published in the GitHub repository seeincodes/skyfi-mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 302 tokens to every session, about $0.0015 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 cursor rules, from other repositories
docs
All documentation files use MDX format with a specific structure.
type-inference
Derive TypeScript types from Zod schemas - no hand-written interfaces for wire shapes.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
boundaries
Package dependency boundaries - tag map and enforced invariants.
react
React 19 SPA invariants - client-only, no fetch in useEffect, Compiler memo policy.
workers-cache
Workers Cache - Cache-Control, gateway exports cache off, RPC vs fetch.