security

security is a command for coding agents from wyattjoh/skills. It costs 0 tokens per session (661 once invoked), scanned A, original, MIT.

Security checks for a Varlock project that compare environment values and source files with the environment schema. They can detect whether resolved secrets appear as plain text in files.

In plain words
What is it for?
Use them to scan files or staged Git changes for leaked environment values, including ignored files when needed, and to audit configuration against the schema.
Why use it?
They help catch accidentally committed or exposed secrets before code is shared. A pre-commit hook can run the scan automatically before each Git commit.

Command

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 commands/wyattjoh/skills/security
Clone the repo
git clone --depth 1 https://github.com/wyattjoh/skills

Wrote 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.

agentmods badge for security

README.md
[![agentmods](https://agentmods.dev/badge/commands/wyattjoh/skills/security.svg)](https://agentmods.dev/commands/wyattjoh/skills/security)
Your own site
<a href="https://agentmods.dev/commands/wyattjoh/skills/security"><img src="https://agentmods.dev/badge/commands/wyattjoh/skills/security.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 661 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.00661
Opus 5 $0.00000 $0.00331
Sonnet 5 $0.00000 $0.00132
Haiku 4.5 $0.00000 $0.00066

Measured 3d ago against content hash 26bb6868d4dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security 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.

skills/varlock/references/commands/security.md · 62 lines

How it starts

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

Security commands: scan, audit

Guardrails that compare your resolved config and code against the schema. Verified against varlock 1.10.0 --help.

scan

Load your varlock config, resolve all sensitive values, then scan files to ensure none of those sensitive values appear in plaintext. Can install itself as a pre-commit hook.

varlock scan [OPTIONS] [<targets> ...]
Arg / Flag Short Purpose
targets Files, dirs, or globs to scan (defaults to the current directory).
--staged Only scan staged git files.
--include-ignored Include git-ignored files in the scan.
--install-hook Set up varlock scan as a git pre-commit hook.
--path <path> -p .env file or dir (trailing /) as the schema entry point. Repeatable.

EXAMPLES: (verbatim from varlock scan --help):

varlock scan                    # Scan non-git-ignored files in current directory
varlock scan --staged           # Only scan staged git files
varlock scan --include-ignored  # Scan all files, including git-ignored ones
varlock scan --path .env.prod   # Use a specific .env file as the schema entry point
varlock scan -p ./envs -p ./overrides  # Use multiple schema entry points
varlock scan --install-hook     # Set up as a git pre-commit hook
varlock scan ./dist             # Scan a specific directory (e.g. a build output folder)
varlock scan ./dist ./public    # Scan multiple directories
varlock scan './dist/**/*.js'   # Scan files matching a glob pattern

audit

Scan source code for environment-variable references and compare them to the keys defined in your schema (surfaces undeclared or unused vars).

Read the full file on GitHub · 62 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. 3d ago First seen · 62 lines · 0 tokens per session scan A 26bb6868d4dd

Subscribe to this mod's changes

security is a command published in the GitHub repository wyattjoh/skills (2 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 661 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.