varlock copilot-instructions.md

Security-focused instructions for reviewing changed code in Varlock, a tool for managing environment variables and secrets. They list risks involving secrets, input handling, process execution, files, cryptography, and AI features.

In plain words
What is it for?
Use them to review pull requests affecting Varlock loaders, commands, plugins, or integrations, while leaving dependency and lockfile checks to dedicated tools.
Why use it?
They focus a code review on ways a change could expose secrets, execute unsafe input, or cross a security boundary.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/dmno-dev/varlock/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/dmno-dev/varlock

Made for: GitHub Copilot.

Per session 474 This file is loaded in full into every session.
When invoked 474 The same file — it is already loaded in full.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00474 $0.00474
Opus 5 $0.00237 $0.00237
Sonnet 5 $0.00095 $0.00095
Haiku 4.5 $0.00047 $0.00047

Measured yesterday against content hash 10334e17e52e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

varlock copilot-instructions.md scanned grade A with 1 finding 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 yesterday.

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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

6. **Risky APIs:** Flag unsafe `child_process`, `vm`, or deserialization from untrusted data.
.github/copilot-instructions.md · 36 lines

How it starts

The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Copilot PR code review (security)

Scope: Focus on code security. Copilot does not review dependency manifests or lockfiles; rely on Dependabot, CodeQL, and the dependency-review workflow for supply chain.

Security checklist (changed lines)

  1. Secrets: No hardcoded API keys, tokens, passwords, or private URLs. Preserve redaction and leak prevention for sensitive env values.
  2. Injection / parsing: Safe handling of user-controlled strings in @env-spec parsing and loaders; avoid eval / new Function on untrusted input.
  3. Process execution: exec / spawn / shell (secret plugins, integrations): avoid shell injection; validate arguments; no untrusted paths.
  4. Filesystem: No path traversal or arbitrary read/write from external input.
  5. Trust boundaries: Document what untrusted config can do; avoid unsafe defaults.
  6. Risky APIs: Flag unsafe child_process, vm, or deserialization from untrusted data.
  7. Crypto: Prefer standard libraries; avoid ad-hoc cryptography.
  8. AI safety: No prompt injection or other unsafe patterns that might allow exfiltration of secrets.

Varlock: Loaders, CLI, packages/plugins, and MCP integrations are high impact.


Copilot Instructions for Varlock

Varlock adds declarative schema to .env files using @env-spec decorator comments — validation, coercion, type safety, redaction/leak prevention for sensitive values, and multi-environment management.

All project conventions live in AGENTS.md — repo structure, bun/workspace usage, scripts, testing, versioning (bumpy changesets), linting, and branch/PR rules. Follow it.

Quick reference:

bun install              # install dependencies
bun run build:libs       # build all libraries (excludes website)
bun run test:ci          # run tests once (CI mode)
bun run lint:fix         # lint with auto-fix — run before completing any task

Before finishing any task: run bun run lint:fix, verify bun run build:libs passes, and add a bumpy changeset if publishable packages changed (see AGENTS.md for details).

Read the full file on GitHub · 36 lines

Changes

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.

  1. yesterday First seen · 36 lines · 474 tokens per session scan A 10334e17e52e

Subscribe to this mod's changes

varlock copilot-instructions.md is an instructions file published in the GitHub repository dmno-dev/varlock (4,238 stars, last pushed 2d ago), licensed MIT. It adds 474 tokens to every session, about $0.0024 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.