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.
Borrowing it
Nothing to install: this file belongs to dmno-dev/varlock. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dmno-dev/varlock/main/AGENTS.mdgit 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/instructions/dmno-dev/varlock/agents-md)<a href="https://agentmods.dev/instructions/dmno-dev/varlock/agents-md"><img src="https://agentmods.dev/badge/instructions/dmno-dev/varlock/agents-md/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/instructions/dmno-dev/varlock/agents-md"><img src="https://agentmods.dev/badge/instructions/dmno-dev/varlock/agents-md.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.01883 | $0.01883 |
| Opus 5.5 | $0.00753 | $0.00753 |
| Sonnet 5.5 | $0.00377 | $0.00377 |
| Haiku 4.5 | $0.00188 | $0.00188 |
Grade A, and why
varlock AGENTS.md 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 12d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project conventions
Repo structure
This is a monorepo managed with bun workspaces and Turborepo:
packages/env-spec-parser— parser for the @env-spec language (PEG.js grammar ingrammar.peggy)packages/varlock— the main package: CLI + library for loading/validating.envfilespackages/varlock-website— docs site (Astro); docs content lives insrc/content/docs/packages/vscode-plugin— VSCode extension for @env-spec language supportpackages/integrations/*— framework integrations (nextjs, vite, astro, ...)packages/native-helpers/*— per-platform npm publishing shells for the native helper binaries (published as@varlock/native-helper-*, versioned in lockstep withvarlock); the binaries themselves are built frompackages/encryption-binary-swift(darwin) andpackages/encryption-binary-rust(linux/win32)packages/utils,packages/plugins— shared internalspackages/varlock-docs-mcp— docs MCP server for external varlock users; do not use it to look things up while working on this repo — read the docs source directly
Package manager
- This repo uses Bun as the package manager (
bun install,bun run, etc.) - Workspace deps use
workspace:*protocol - Use catalog for any potentially common dependencies
- CI workflows use
bun runto execute scripts andbunxfor one-off commands
Building
bun run buildat the repo root builds all packages via Turborepo, in dependency order- To build a single package, go through turbo so its workspace deps build first:
bunx turbo run buildfrom the package directory, orbunx turbo run build --filter=<pkg>from the root - Do not build a package with
bun run --filter <pkg> build: bun's filter does not build the package's workspace dependencies, and some builds require their dist output to exist (e.g. varlock's d.ts bundling inlines the emitted declarations frompackages/utils, so it fails if that package was never built)
Scripts
- Write any scripts which may end up being saved in TypeScript (
.ts), not JavaScript- throwaway/one-off code is fine in JS
- Execute scripts using
bun run, notnode- e.g.
bun run scripts/release-preview.ts - Bun runs
.tsfiles natively — no compile step needed
- e.g.
- Scripts in
scripts/at the repo root are monorepo-level utilities, while specific packages may have their ownscriptsfolder
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.
- 12d ago Changed · +1 lines · +41 tokens per session e752ac63aca9
- 1mo ago Changed · +6 lines · +142 tokens per session ee2102c2cfeb
- 1mo ago First seen · 84 lines · 1,700 tokens per session scan A 25cdd0837dab
varlock AGENTS.md is an instructions file published in the GitHub repository dmno-dev/varlock (4,830 stars, last pushed 5d ago), licensed MIT. It adds 1,883 tokens to every session, about $0.0075 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.