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.
npx skills add buhaistrikalo/envskill --skill bundled_skillgit clone --depth 1 https://github.com/buhaistrikalo/envskillWrote 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.
[](https://agentmods.dev/skills/buhaistrikalo/envskill/bundled_skill)<a href="https://agentmods.dev/skills/buhaistrikalo/envskill/bundled_skill"><img src="https://agentmods.dev/badge/skills/buhaistrikalo/envskill/bundled_skill/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.
<a href="https://agentmods.dev/skills/buhaistrikalo/envskill/bundled_skill"><img src="https://agentmods.dev/badge/skills/buhaistrikalo/envskill/bundled_skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00027 | $0.00573 |
| Opus 5 | $0.00014 | $0.00287 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
envskill 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 10d 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.
This is a copy
100% identical to envskill — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
envskill
Use envskill as the boundary between secret values and commands that need them.
First-time setup
If the CLI or store is not configured, ask the user to run the guided setup:
envskill setup
It initializes the owner-only store, detects supported agent hosts, installs this skill, and performs a value-free verification. To import an explicitly selected legacy dotenv file without displaying its values, use:
envskill setup --agent all --import ~/.env
Existing secret names are kept by default. Only add --overwrite when the user
explicitly wants imported names to replace existing ones. A different existing
skill copy is never replaced unless --force is explicitly supplied.
Workflow
-
Discover names with
envskill list. This command prints names only. -
Check a required name with
envskill has NAME. -
Run the target command with the narrowest credential scope:
envskill run --only NAME1,NAME2 -- command args... -
If a variable is missing, tell the user its name and ask them to run:
envskill set NAMEThe command prompts for the value without echoing it. Never ask the user to paste a secret into chat.
Hard Rules
- Never open, read, search, copy, summarize, or commit the envskill store.
- Never reveal values through
env,printenv,set, shell expansion, logs, or debug output. - Never use
envskill run --allunless the user explicitly requests broad exposure. - The child starts with a minimal functional environment. Use
--inherit NAMEonly when the target command requires a specific non-secret parent variable or capability. - Never place secret values in command arguments, prompts, source files, patches, or test fixtures.
- A successful command is proof of availability. Do not inspect the injected value afterward.
- If a command fails, report the variable name or command error, not credential contents.
Rotation
envskill reads its store on every invocation. After the user runs envskill set NAME, retry the original command through envskill run; restarting the agent is unnecessary.
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.
- 10d ago First seen · 69 lines · 27 tokens per session scan A b81ebbbd08a4
envskill is a skill published in the GitHub repository buhaistrikalo/envskill (6 stars, last pushed 16d ago), licensed MIT. It adds 27 tokens to every session and 573 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to envskill, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
cis-aws-compute-3.6
Ensure secrets are not passed as container environment variables in Amazon ECS task definitions.
configuration-management
Manage application configuration across environments with layered config loading, environment variables, secrets management, and validation. Covers 12-factor app patterns and config file formats. Triggers on configuration management, environment variables, or settings architecture requests.
varlock
Secure environment variable management with Varlock. Use when handling secrets, API keys, credentials, or any sensitive configuration. Ensures secrets are never exposed in terminals, logs, traces, or Claude's context. Trigger phrases include "environment variables", "secrets", ".env", "API key", "credentials"…
js-secrets-extraction
Analyze JS bundles and source maps for hardcoded secrets, API keys, JWTs, and internal endpoints.
performing-kubernetes-etcd-security-assessment
Assess the security posture of Kubernetes etcd clusters by evaluating encryption at rest, TLS configuration, access controls, backup encryption, and network isolation.
google-dorks-catalog
High-precision Google dorks for exposed configs, secrets, and credentials -- real-world validated.