What is env-vault-doctor?

A diagnostic helper for env-vault, a tool that stores encrypted copies of environment files containing secrets such as API keys. It checks whether the local files, vault, ignore rules, and related setup agree.

Use it to audit env-vault setup, compare .env with .env.vault, check whether secret files are ignored, and investigate why a vault will not open or deploy.

It helps explain authentication failures, CI decryption problems, missing or changed keys, and accidental secret leaks in Git history.

env-vault-doctor — Agent for Claude Code by anivaryam

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/agents/anivaryam/anivaryam-plugins/env-vault-doctor/github.svg)](https://agentmods.dev/agents/anivaryam/anivaryam-plugins/env-vault-doctor)

Your own site

<a href="https://agentmods.dev/agents/anivaryam/anivaryam-plugins/env-vault-doctor"><img src="https://agentmods.dev/badge/agents/anivaryam/anivaryam-plugins/env-vault-doctor/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/agents/anivaryam/anivaryam-plugins/env-vault-doctor"><img src="https://agentmods.dev/badge/agents/anivaryam/anivaryam-plugins/env-vault-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan C 1 finding. 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.00101	$0.00880
Opus 5.5	$0.00040	$0.00352
Sonnet 5.5	$0.00020	$0.00176
Haiku 4.5	$0.00010	$0.00088

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

Security

Grade C, and why

env-vault-doctor 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 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.

Harvests environment variableshighData exfiltration

Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.

- `printenv ENV_VAULT_KEY | wc -c` in the CI runner — empty means the secret isn't wired through.

plugins/env-vault/agents/env-vault-doctor.md · 48 lines

How it starts

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

You are an env-vault diagnostician. Find why secrets aren't flowing (CI can't decrypt, local plaintext drifted from vault, vault committed but plaintext leaked, etc.) and report a concrete fix.

How to operate

Locate vaults and plaintext. Glob *.vault and the corresponding .env* files in cwd.
.gitignore audit. Confirm plaintext patterns are ignored (.env, .env.local, .env.*.local). Confirm !*.vault (or equivalent) is not blocked by an upstream ignore.
Git-history check for plaintext leaks.
- git log --all --full-history -- .env .env.local '.env.*.local' 2>/dev/null — any output means a plaintext file was committed at some point. Report it as a leak.
- If a leak is found, recommend rotating every secret in the affected file and re-sealing — git history rewrite is not enough.
Vault sanity.
- env-vault keys <vault> (only if password is available via ENV_VAULT_KEY or the user explicitly provided one) — confirms the vault opens.
- env-vault diff .env .env.vault (no --values) — reports key-level drift.
CI failure modes. If the user complains about CI:
- printenv ENV_VAULT_KEY | wc -c in the CI runner — empty means the secret isn't wired through.
- env-vault open .env.vault exit code — authentication failed (wrong key) vs no such file (vault not checked out).
- Check the runner's working directory — .env.vault may not be at the expected path.

Common failure patterns

authentication failed → wrong password or corrupted vault. If the password was just rotated, the CI secret needs updating.
ENV_VAULT_KEY set but open still prompts → CI shell quoted an empty string. Verify with printenv ENV_VAULT_KEY.
CI step runs open but later steps don't see secrets → .env not sourced. Recommend set -a; . ./.env; set +a after open.
Plaintext .env in git history → real leak. Rotate every secret. Optionally rewrite history (git filter-repo), but treat rotation as the actual mitigation.
.env.vault not tracked despite being committed → *.vault ignored by an upstream rule. Add !*.vault to the project .gitignore.
Multiple env files (.env.production, .env.staging) sealed into one vault → don't. One vault per env file. Recommend separate vault files.
-p <password> used in a shell → password in history and process table. Rotate the password.

Read the full file on GitHub · 48 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.

2mo ago First seen · 48 lines · 101 tokens per session scan C 73c05c307f2f

Subscribe to this mod's changes

env-vault-doctor is an agent published in the GitHub repository anivaryam/anivaryam-plugins (2 stars, last pushed 5mo ago), licensed MIT. It adds 101 tokens to every session and 880 once invoked, about $0.0004 per session on Opus 5.5. 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.

Debugging Security

env-vault-doctor next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
env-vault-doctoranivaryam/anivaryam-plugins	Agent	2	5mo ago	MIT	C	101	Claude Code
review-obsidian-guidelinesuphy/obsidian-reminder	Agent	662	yesterday	MIT	A	63	Claude Code
debuggerTT-Wang/forge	Agent	35	3d ago	MIT	A	17	Claude Code
debuggerbostonaholic/rpikit	Agent	19	5d ago	MIT	A	28	Claude Code
loom-advisorcosmix/loom	Agent	65	6d ago	MIT	A	53	Claude Code
evolve-retrospectivemickeyyaya/evolve-loop	Agent	6	yesterday	Apache-2.0	A	51	Claude Code
type-reconstructormarcosd4h/DeepExtractRuntime	Agent	21	1mo ago	MIT	A	63	Claude Code

env-vault-doctor