More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    env file drift checker

    1

    Compare every .env file with your .env.example: missing and extra keys, empty values, weak secrets and risky production settings. Values are always masked.

    $5.29

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    About this skill

    "Works on staging, crashes in prod" is usually one missing env var.

    Point it at a project folder. It finds .env.example (or .env.sample / .env.template) and compares every other .env file against it. You get a key matrix (which file has which key), missing and undocumented keys, empty values, and values that are still template placeholders. It also flags weak or short secrets, and production files with DEBUG on, localhost URLs, plain http:// endpoints or NODE_ENV=development, plus secrets reused across environments. Secret values are never printed, only masked. It handles export KEY=, quotes, comments and duplicate keys the way dotenv loaders do.

    What it does

    • Key matrix across .env.example, development, staging and production
    • Missing, extra, empty, placeholder and duplicate keys
    • Weak secrets: short, low-entropy or default passwords and placeholder URLs
    • Production traps: DEBUG=true, NODE_ENV=development, localhost/127.0.0.1, plain http://
    • Secrets reused across environments
    • Masked output plus JSON for CI. Exit code 1 on errors

    Who it's for

    Developers and DevOps engineers juggling several environments, and anyone onboarding to a project with a stale .env.example.

    Limits

    Reads dotenv-style files only. It does not read Kubernetes secrets, Vault or cloud secret managers. Production is detected by file name (prod/production/live), which you can change with --prod.

    What's included

    • SKILL.md: workflow, commands, how to explain results
    • scripts/: the tool (standard-library Python)
    • references/: sources
    • examples/: sample inputs used in the demo (all made up)
    • tests/: unit tests (Python 3.8 / 3.9 / 3.13)

    Standard-library Python only. No API keys, no network calls, no installs.

    Reads dotenv-style files only. It does not read Kubernetes secrets, Vault or cloud secret managers.
    Production is detected by file name (prod/production/live), which you can change with --prod.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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 today

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listedtoday

    What's inside

    Frequently Asked Questions

    No. Values are masked (first characters only) in text and JSON output.

    dotenv syntax: KEY=VALUE, export KEY=VALUE, quotes, inline comments.

    No. It reads local files only.

    New in DevOps & Cloud