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/i4ctime/q-ring/env-file-safetygit clone --depth 1 https://github.com/I4cTime/q-ringWrote 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/i4ctime/q-ring/env-file-safety)<a href="https://agentmods.dev/rules/i4ctime/q-ring/env-file-safety"><img src="https://agentmods.dev/badge/rules/i4ctime/q-ring/env-file-safety.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.00189 |
| Opus 5 | $0.00000 | $0.00095 |
| Sonnet 5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
env-file-safety 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 3d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 3d ago First seen · 14 lines · 0 tokens per session scan A df51e6a9d9a8
env-file-safety is a cursor rule published in the GitHub repository I4cTime/q-ring (4 stars, last pushed 3d ago), licensed AGPL-3.0. It costs nothing until one of its globs matches a file; then it loads 189 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
speclock
SpecLock project constraints — enforced automatically.
infura-mcp-server
Cursor rule "infura-mcp-server" from Qbandev/infura-mcp-server, covering infura mcp server project context, 📚 ai assistant resources, project overview, key statistics and technical architecture.
mcp-tools-readme
Keep README in sync when MCP tools change.
task-plannning
When tickets have been assigned or revising the implementation plan.
task-status-update-rule
Always When updating the status of a task.
md-feedback-workflow
This project uses md-feedback for structured human review of implementation plans.