Varlock is a configuration system for environment-variable files that gives coding agents schemas and validation rules without revealing secret values. Developers use it to manage, validate, load, and protect application configuration across environments.
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/dmno-dev/varlockWrote 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/dmno-dev/varlock/cursor-rules-location)<a href="https://agentmods.dev/rules/dmno-dev/varlock/cursor-rules-location"><img src="https://agentmods.dev/badge/rules/dmno-dev/varlock/cursor-rules-location/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/dmno-dev/varlock/cursor-rules-location"><img src="https://agentmods.dev/badge/rules/dmno-dev/varlock/cursor-rules-location.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.00479 | $0.00479 |
| Opus 5.5 | $0.00192 | $0.00192 |
| Sonnet 5.5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
cursor-rules-location 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- cursor-rules-location — 94% identical, 1 lines differ
- cursor_rules_location — 92% identical, 7 lines differ
- location-rule — 89% identical, 6 lines differ
- cursor-rules-location — 89% identical, 13 lines differ
- cursor-rules-location — 89% identical, 13 lines differ
- cursor-rules-location — 84% identical, 15 lines differ
What it actually says
description: Cursor Rules Location globs: *.mdc
Cursor Rules Location
Rules for placing and organizing Cursor rule files in the repository.
actions:
-
type: reject conditions:
- pattern: "^(?!\.\/\.cursor\/rules\/.*\.mdc$)" message: "Cursor rule files (.mdc) must be placed in the .cursor/rules directory"
-
type: suggest message: | When creating Cursor rules:
-
Always place rule files in PROJECT_ROOT/.cursor/rules/:
.cursor/rules/ ├── your-rule-name.mdc ├── another-rule.mdc └── ... -
Follow the naming convention:
- Use kebab-case for filenames
- Always use .mdc extension
- Make names descriptive of the rule's purpose
-
Directory structure:
PROJECT_ROOT/ ├── .cursor/ │ └── rules/ │ ├── your-rule-name.mdc │ └── ... └── ... -
Never place rule files:
- In the project root
- In subdirectories outside .cursor/rules
- In any other location
-
examples:
-
input: |
Bad: Rule file in wrong location
rules/my-rule.mdc my-rule.mdc .rules/my-rule.mdc
Good: Rule file in correct location
.cursor/rules/my-rule.mdc output: "Correctly placed Cursor rule file"
metadata: priority: high version: 1.0
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 First seen · 80 lines · 479 tokens per session scan A 1f53b8cfacdd
cursor-rules-location is a cursor rule published in the GitHub repository dmno-dev/varlock (4,708 stars, last pushed today), licensed MIT. It adds 479 tokens to every session, about $0.0019 per session on Opus 5.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-30.
Other cursor rules, from other repositories
090-env-schema
090: Environment variable schema.
github-workflow
GitHub invariants — standard flow on listed use cases; no issue spam; tick linked checklists before merge.
secrets
Secrets management, environment variables, and secure configuration.
skill-selection
Pick the fewest skills for this task. Core lifecycle for non-trivial work; extras only on a matching signal. Catalog is using-agent-skills, not this rule.
00-user-context
Always-on user identity, engineering preferences, and communication constraints for mamahoos.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.