secrets

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

A collection of commands for encrypting, viewing, locking, generating, and caching sensitive values such as passwords and deployment keys. It uses Varlock and can integrate with device security features or the macOS Keychain.

In plain words
What is it for?
Use it to encrypt environment values, safely reveal them, manage encryption keys, run the encryption daemon, and handle deployment secrets.
Why use it?
It keeps secrets out of shell history, committed files, and terminal scrollback while still allowing approved users and tools to use them.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/wyattjoh/skills/secrets.svg)](https://agentmods.dev/commands/wyattjoh/skills/secrets)
Your own site
<a href="https://agentmods.dev/commands/wyattjoh/skills/secrets"><img src="https://agentmods.dev/badge/commands/wyattjoh/skills/secrets.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 1,117 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.01117
Opus 5 $0.00000 $0.00558
Sonnet 5 $0.00000 $0.00223
Haiku 4.5 $0.00000 $0.00112

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

Security

Grade A, and why

secrets 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/secrets.md · 124 lines

How it starts

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

Secrets & encryption: encrypt, reveal, lock, generate-key, keychain, cache

Commands for handling @sensitive values: device-local encryption, secure viewing, the encryption daemon, deployment keys, macOS Keychain, and the value cache. Verified against varlock 1.10.0 --help.

encrypt

Encrypt a value using device-local encryption (Secure Enclave / TPM / file-based), producing a varlock("local:...") reference that is safe to commit. Single-value mode reads from stdin (or prompts) so secrets stay out of shell history.

varlock encrypt [OPTIONS]
Flag Purpose
--file <file> Encrypt all @sensitive plaintext values in a .env file, in place.

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

echo "$MY_SECRET" | varlock encrypt    # Encrypt a value from stdin (non-interactive, agent-friendly)
varlock encrypt                        # Prompt interactively for a value
varlock encrypt --file .env.local      # Encrypt @sensitive plaintext values in a file in-place

reveal

Securely view the plaintext of sensitive variables. Values are shown in an alternate screen buffer so they do not persist in scrollback.

varlock reveal [OPTIONS] [<key>]
Flag Purpose
--copy Copy the value to the clipboard instead of displaying it (auto-clears after 10s).
--path <path> / -p Entry-point .env file/dir. Repeatable.
--env <env> Set the environment.

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

varlock reveal                  # Interactive picker to select and reveal values
varlock reveal MY_SECRET        # Reveal a specific variable
varlock reveal MY_SECRET --copy # Copy value to clipboard (auto-clears after 10s)

Read the full file on GitHub · 124 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 · 124 lines · 0 tokens per session scan A 559be3eea4da

Subscribe to this mod's changes

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