What is secrets-env-management?

A safety process for handling environment variables and credentials such as API keys, tokens, and private keys. It uses placeholder examples instead of exposing real secret values.

Use it to document required variables, update .env.example files, check ignore rules, investigate possible leaks, and plan credential rotation.

It reduces the risk of committing credentials to source control or sharing them in documentation.

How YankielDBC2/codex-skills-library configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to YankielDBC2/codex-skills-library. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/YankielDBC2/codex-skills-library/main/.agents/skills/secrets-env-management/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/YankielDBC2/codex-skills-library

Made for: Codex.

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/skills/yankieldbc2/codex-skills-library/secrets-env-management/github.svg)](https://agentmods.dev/skills/yankieldbc2/codex-skills-library/secrets-env-management)

Your own site

<a href="https://agentmods.dev/skills/yankieldbc2/codex-skills-library/secrets-env-management"><img src="https://agentmods.dev/badge/skills/yankieldbc2/codex-skills-library/secrets-env-management/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/skills/yankieldbc2/codex-skills-library/secrets-env-management"><img src="https://agentmods.dev/badge/skills/yankieldbc2/codex-skills-library/secrets-env-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 333 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.00029	$0.00333
Opus 5.5	$0.00012	$0.00133
Sonnet 5.5	$0.00006	$0.00067
Haiku 4.5	$0.00003	$0.00033

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

Security

Grade A, and why

secrets-env-management 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.

.agents/skills/secrets-env-management/SKILL.md · 51 lines

What it actually says

Secrets Env Management

Goal

Help projects use environment variables safely without exposing secrets.

When to use

Use when adding environment variables, reading .env.example, documenting credentials, configuring deployment secrets, or investigating leaked keys.

When not to use

Do not use to reveal, print, decode, test, or share secret values.

Inputs

Inspect .env.example, deployment docs, config files, required variable names, and .gitignore. Do not open real secret files unless the user explicitly asks for a safety review, and never reproduce values.

Workflow

Identify required variable names without printing values.
Ensure real env files are ignored by git.
Create or update .env.example with placeholders only.
Document where variables are configured locally and in deployment.
Add validation for required variables when useful.
Warn when production/live credentials appear exposed.
Recommend rotation for any credential that may have been shared.

Safety rules

Never print full secrets.
Never commit .env, agent.env, PEM files, or private keys.
Never place live values in examples.
Prefer project-specific credentials with least privilege.

Validation

Run secret scan, git status, and any env validation script added to the project.

Final response

Report variable names only, files changed, validation commands, and rotation recommendations without revealing secret values.

Files

What ships with it

4 files 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.

2mo ago First seen · 51 lines · 29 tokens per session scan A 769e5a62bbe9

Subscribe to this mod's changes

secrets-env-management is a skill published in the GitHub repository YankielDBC2/codex-skills-library (13 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 333 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.