project

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

A group of Varlock commands for setting up environment-variable files, generating code from their schema, installing plugins, and handling routine project tasks. Varlock uses a schema to describe variables such as their types and whether they are required or secret.

In plain words
What is it for?
Use it to initialise Varlock in a project, create or update an environment schema, and generate typed environment modules.
Why use it?
It reduces manual setup and keeps generated environment code consistent with the schema. The setup can also run non-interactively in automated workflows.

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/project
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 project

README.md
[![agentmods](https://agentmods.dev/badge/commands/wyattjoh/skills/project.svg)](https://agentmods.dev/commands/wyattjoh/skills/project)
Your own site
<a href="https://agentmods.dev/commands/wyattjoh/skills/project"><img src="https://agentmods.dev/badge/commands/wyattjoh/skills/project.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 804 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.00804
Opus 5 $0.00000 $0.00402
Sonnet 5 $0.00000 $0.00161
Haiku 4.5 $0.00000 $0.00080

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

Security

Grade A, and why

project 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 4d 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/project.md · 107 lines

How it starts

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

Project & tooling: init, codegen, install-plugin, complete, telemetry, help

Setup, code generation, plugins, and housekeeping commands. Verified against varlock 1.10.0 --help.

init

Interactive onboarding: scan for .env files, create a .env.schema from an existing .env.example / .env.sample, and add varlock to package.json (if applicable). Run it in a directory containing .env or .env.* files.

varlock init [OPTIONS]
Flag Purpose
--agent Non-interactive mode for agent / automation workflows.

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

varlock init                    # Run in the current directory
varlock init --agent            # Run non-interactively (agent/automation friendly)
cd path/to/your/project && varlock init

codegen

Generate code (types and env modules) from the schema. Uses only non-environment-specific schema info, so output is deterministic. Add a per-language generator decorator to the schema for each output; run codegen when a generator has auto=false (disabling automatic generation during load / run).

varlock codegen [OPTIONS]
Flag Short Purpose
--path <path> -p .env file or directory as the entry point. Repeatable.

Generator decorators (from the help text): @generateTsTypes(path=env.d.ts), @generatePythonEnv(path=env.py), @generateRustEnv(path=src/env.rs), @generateGoEnv(path=env/env.go), @generatePhpEnv(path=Env.php). See ../env-schema.md.

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

varlock codegen                    # Generate using the default schema
varlock codegen --path .env.prod   # Generate from a specific .env file

Read the full file on GitHub · 107 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. 4d ago First seen · 107 lines · 0 tokens per session scan A cfbda109ac6c

Subscribe to this mod's changes

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