- Home
- Skills
- DevOps & Cloud
- Env Drift Check
More screenshots
Works with the AI Agents you already use
Env Drift Check
Keep .env.example in step with your code and keep .env files out of git: missing and stale variables, real secrets in the example file, unignored .env files and secrets with public prefixes.
$5
Env Drift Check
Example session with this skill installed
Check this project with env-drift-check.
- Read your context and instructions
- Compiled the env drift check
$ python3 scripts/check_env.py examples/risky
BLOCK .env.example:2 E01 REAL_SECRET_IN_EXAMPLE
PAYMENT_API_SECRET=<redacted, 20 chars>
Why: The example env file, which is meant to be committed and shared, holds what looks like a real secret value instead of a placeholder.
Safer: Rotate that secret, and leave the value empty or use a placeholder such as your-key-here in the example file.
BLOCK .env.example:3 E03 SECRET_WITH_PUBLIC_PREFIX
BLOCK .env.local E02 ENV_FILE_NOT_IGNORED
REVIEW .env.example:4 E12 UNUSED_IN_EXAMPLE
REVIEW .env.example:5 E14 DUPLICATE_IN_EXAMPLE
REVIEW src/server.js:3 E11 MISSING_FROM_EXAMPLE
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 5 files, 4 with env content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
"Works on my machine" often means a variable the code reads is missing from .env.example. This skill compares every variable your code reads with your example env file, finds the gaps and leftovers, and flags env mistakes that leak secrets.
Your agent runs a scanner on the project. It reads JavaScript, TypeScript, Python, PHP, Ruby, Go, Prisma and Compose files, your example env files and .gitignore. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. The report never prints values from your real .env files.
What it checks
BLOCK
- E01: a real-looking secret value in the example env file
- E02: a real .env file that .gitignore does not ignore
- E03: a secret-looking variable with a public prefix (NEXT_PUBLIC_, VITE_, REACT_APP_ and similar)
REVIEW
- E11: a variable the code reads that the example file does not list
- E12: an example entry nothing reads
- E13: env variables used with no example file at all
- E14: the same key twice in the example file
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example project, and the real report the scanner produces on the risky one
Limits It finds variable names written literally in code. Names built at run time or read through config libraries are not seen. Every .gitignore in the project, and above it up to the repository root, is applied the way git applies it. NOT FLAGGED is not a guarantee.
Finds literally written variable names only. Global git excludes are not read. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Requires
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The examples include sample env files with made-up values for the scanner to find.