sops-secrets

A standard for storing configuration secrets encrypted with sops and age, while keeping encrypted files in Git and plaintext out of files, logs, and commits.

In plain words
What is it for?
Use it to encrypt YAML, JSON, or environment files, manage age recipients, and connect encrypted configuration to Flux or OpenTofu at runtime.
Why use it?
It lets teams review secret-related changes without exposing the secret values and limits when plaintext secrets exist.

Skill for Claude CodeCodex

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 skills/fmind/dotfiles/sops-secrets
Any agent
npx skills add fmind/dotfiles --skill sops-secrets
Clone the repo
git clone --depth 1 https://github.com/fmind/dotfiles

Made for: Claude Code, Codex.

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,532 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.00032 $0.01532
Opus 5 $0.00016 $0.00766
Sonnet 5 $0.00006 $0.00306
Haiku 4.5 $0.00003 $0.00153

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

Security

Grade A, and why

sops-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 2d 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/sops-secrets/SKILL.md · 65 lines

How it starts

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

Secrets Standard (sops 3.13+ / age)

Canonical workflow for sops (structured-file encryption) with age (modern key pairs) — encrypted secrets live in git next to the code they configure, and plaintext exists only in memory. This operationalizes the global "No Secrets in Output" rule: no plaintext secret ever touches disk, logs, or a commit.

1. Core Model

  • age provides the key pair: one private key per machine/human, public recipients everywhere. Prefer age over PGP (simpler, no keyservers) and over cloud KMS for solo/portable use; add a gcp_kms recipient alongside age only when a team needs central revocation.
  • sops encrypts the values of YAML/JSON/ENV files — keys stay readable, so diffs review cleanly and git log still tells you which secret changed, never what it is.
  • Naming Convention: encrypted files are committed as *.enc.yaml / *.enc.json / *.enc.env; the sops.yaml rules key off that suffix, and any plaintext siblings stay gitignored.
  • Policy As File: .sops.yaml at the repo root (sops.yaml) declares which paths get encrypted and for which recipients — creation is automatic, ad-hoc flags are never needed.

2. Key Management

  1. Generate once per machine: age-keygen -o ~/.config/sops/age/keys.txt — sops' default key location; print the public half anytime with age-keygen -y ~/.config/sops/age/keys.txt.
  2. Distribute only the public key: paste it as the age: recipient in each repo's sops.yaml.
  3. Back up the private key in a password manager. Never commit it anywhere — in particular never chezmoi add it, since the dotfiles repository is public.
  4. Rotate by adding the new recipient to .sops.yaml, running sops updatekeys <file> on every encrypted file, then removing the old recipient and repeating; sops rotate -i <file> re-keys the data key after a suspected exposure.

3. Daily Workflow

sops edit secrets.enc.yaml                      # create or edit (decrypts to $EDITOR, re-encrypts on save)
sops -e -i config.yaml                          # encrypt an existing file in place (then rename to *.enc.yaml)
sops -d secrets.enc.yaml                        # decrypt to stdout — for piping, never for redirecting to a file
sops exec-env secrets.enc.env 'mise run watch'  # inject as env vars, memory-only (preferred)
sops exec-file secrets.enc.json 'tool --config {}'  # tools that require a file path get a tmpfs one

Read the full file on GitHub · 65 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 65 lines · 32 tokens per session scan A d61833a46fd2

Subscribe to this mod's changes

sops-secrets is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 1,532 once invoked, about $0.0002 per session on Opus 5. 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.

Related

Other skills, from other repositories

dotfiles-bootstrap

Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.

sebastienrousseau/dotfiles · 88 tokens

vibe

Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…

sebastienrousseau/dotfiles · 137 tokens

aiq-research

Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.

laurigates/dotfiles · 25 tokens

obsidian-bases

Obsidian Bases database feature for YAML-based interactive note views. Use when creating .base files, writing filter queries, building formulas, configuring table/card views, or working with Obsidian properties and frontmatter databases.

laurigates/dotfiles · 49 tokens

telegram

Send notifications, interactive questions, or multiple-choice polls to the user via Telegram. Use when the user asks to be notified ("ping me", "notify me on Telegram", "ask me when..."), when a long-running task finishes and the user is likely away, when an irreversible action needs out-of-band confirmation, or when…

laurigates/dotfiles · 117 tokens

chezmoi-expert

Comprehensive chezmoi dotfiles management expertise including templates, cross-platform configuration, file naming conventions, and troubleshooting. Covers source directory management, reproducible environment setup, and chezmoi templating with Go templates. Use when user mentions chezmoi, dotfiles, cross-platform…

laurigates/dotfiles · 88 tokens