A command that encrypts a .env file, which commonly stores application settings and passwords, into a .env.vault file. It asks for a password unless an environment variable supplies one.

Use it to seal a .env file, check that it is ignored by Git, avoid exposing passwords in shell history, and verify that the encrypted file can be opened back correctly.

It helps protect environment secrets when they need to be stored or shared, while warning about unsafe password handling and untracked files.

seal — Command for Claude Code by anivaryam/anivaryam-plugins

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.

Clone the repo

git clone --depth 1 https://github.com/anivaryam/anivaryam-plugins

Made for: Claude Code.

Or install env-vault, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 1 agent.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/anivaryam/anivaryam-plugins/seal/github.svg)](https://agentmods.dev/commands/anivaryam/anivaryam-plugins/seal)

Your own site

<a href="https://agentmods.dev/commands/anivaryam/anivaryam-plugins/seal"><img src="https://agentmods.dev/badge/commands/anivaryam/anivaryam-plugins/seal/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/anivaryam/anivaryam-plugins/seal"><img src="https://agentmods.dev/badge/commands/anivaryam/anivaryam-plugins/seal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 244 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00025	$0.00244
Opus 5.5	$0.00010	$0.00098
Sonnet 5.5	$0.00005	$0.00049
Haiku 4.5	$0.00003	$0.00024

Measured 2mo ago against content hash d62b94071f95, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

seal 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 2mo 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.

plugins/env-vault/commands/seal.md · 17 lines

What it actually says

Run env-vault seal $ARGUMENTS.

Before running:

If no file argument is given, default to .env and confirm with the user.
Refuse to seal a file that's already a vault (starts with #:env-vault:v1:ruc).
Recommend against passing -p <password> directly — the password ends up in shell history and the process table. Use the interactive prompt or ENV_VAULT_KEY env var instead.
Confirm .env is gitignored. If not, warn the user and offer to add it.
If a vault file already exists at the output path, confirm overwrite with the user before running.

After running, confirm the vault round-trips: env-vault open <vault> -o /tmp/.env.check and diff against the original. If they don't match, surface the error and stop — don't commit a broken vault.

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.

2mo ago First seen · 17 lines · 25 tokens per session scan A d62b94071f95

Subscribe to this mod's changes

seal is a command published in the GitHub repository anivaryam/anivaryam-plugins (2 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 244 once invoked, about $0.0001 per session on Opus 5.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.