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.
npx agentmods add commands/wyattjoh/skills/coregit clone --depth 1 https://github.com/wyattjoh/skillsWrote 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/commands/wyattjoh/skills/core)<a href="https://agentmods.dev/commands/wyattjoh/skills/core"><img src="https://agentmods.dev/badge/commands/wyattjoh/skills/core.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01591 |
| Opus 5 | $0.00000 | $0.00796 |
| Sonnet 5 | $0.00000 | $0.00318 |
| Haiku 4.5 | $0.00000 | $0.00159 |
Grade C, and why
core scanned grade C 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 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
> 📍 Embed in shell commands with `sh -c`, e.g. `sh -c 'do-something --token $(varlock printenv MY_TOKEN)'`. How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core commands: load, run, printenv, explain
The daily-driver resolution commands. All accept the common resolution
flags (-p/--path, --env,
--clear-cache, --skip-cache). Verified against varlock 1.10.0 --help.
load
Load env according to the schema, resolve + validate values, and print them. Sensitive values are redacted. The primary local-debug and CI-summary command.
varlock load [OPTIONS]
| Flag | Short | Purpose |
|---|---|---|
--format [format] |
-f |
Output format: pretty (default), json, env, shell, json-full. |
--agent |
Agent-safe mode: redact sensitive values (defaults to JSON if --format unset). |
|
--compact |
Compact output (json-full: no indentation; env/shell: skip undefined values). | |
--show-all |
When load is failing, show all items, not only failing ones. | |
--env <env> |
Set the environment (overridden by @currentEnv if present). |
|
--path <path> |
-p |
Entry-point .env file/dir. Repeatable. |
--summary-stderr |
Also write the pretty (redacted) summary to stderr. | |
--summary-file <file> |
Also write the pretty summary to a file (e.g. $GITHUB_STEP_SUMMARY). |
|
--clear-cache |
Clear cache and re-resolve. | |
--skip-cache |
Skip cache for this invocation. |
EXAMPLES: (verbatim from varlock load --help):
varlock load # Load and validate with pretty output
varlock load --format json # Output in JSON format
eval "$(varlock load --format shell)" # Load vars into current shell (useful with direnv)
varlock load --show-all # Show all items when validation fails
varlock load --path .env.prod # Load from a specific .env file
varlock load -p ./envs -p ./overrides # Load from multiple directories
varlock load --compact # Use compact format - skips undefined values, no indentation for json-full
varlock load --env production # Load for a specific environment (⚠️ ignored if using @currentEnv!)
varlock load --format json-full --summary-stderr # JSON on stdout + redacted human summary on stderr
varlock load --format json-full --summary-file /tmp/summary.txt # JSON on stdout + redacted human summary written to file
varlock load --agent # Agent-safe JSON output with sensitive values redacted
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.
- 4d ago First seen · 128 lines · 0 tokens per session scan C c6b5376757c8
core 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 1,591 tokens. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.