env

env is a command for Claude Code from build-with-dhiraj/ai-workflow-framework-portability-kit. It costs 35 tokens per session (2,198 once invoked), scanned A, original, MIT.

A set of commands for managing Vercel project environment variables, which are settings such as service keys kept outside source code. It can list, download, add, remove, and compare these settings without printing secret values.

In plain words
What is it for?
Use it to inspect variable names, pull Vercel settings into a local file, add or remove variables, and compare local and hosted configuration.
Why use it?
Environment settings often differ between local development and hosted environments, and exposing their values can create a security risk. These commands help keep the settings aligned while showing only safe metadata.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is source <(grep -v '^#' .env.local | sed 's/^/export /') && node scripts/migrate.js.

Part of the vercel-plugin plugin — 47 skills, 6 commands, 3 agents, 1 MCP server shipped together

Good fit Use it to inspect variable names, pull Vercel settings into a local file, add or remove variables, and compare local and hosted configuration.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/build-with-dhiraj/ai-workflow-framework-portability-kit
agentmods
npx agentmods add commands/build-with-dhiraj/ai-workflow-framework-portability-kit/env

Made for: Claude Code.

Or install vercel-plugin, the plugin that ships this one along with the rest of its 47 skills, 6 commands, 3 agents, 1 MCP server.

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.

agentmods badge for env

README.md
[![agentmods](https://agentmods.dev/badge/commands/build-with-dhiraj/ai-workflow-framework-portability-kit/env/github.svg)](https://agentmods.dev/commands/build-with-dhiraj/ai-workflow-framework-portability-kit/env)
Your own site
<a href="https://agentmods.dev/commands/build-with-dhiraj/ai-workflow-framework-portability-kit/env"><img src="https://agentmods.dev/badge/commands/build-with-dhiraj/ai-workflow-framework-portability-kit/env/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.

agentmods 80×15 button for env

Your own site · 80×15
<a href="https://agentmods.dev/commands/build-with-dhiraj/ai-workflow-framework-portability-kit/env"><img src="https://agentmods.dev/badge/commands/build-with-dhiraj/ai-workflow-framework-portability-kit/env.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,198 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.02198
Opus 5.5 $0.00014 $0.00879
Sonnet 5.5 $0.00007 $0.00440
Haiku 4.5 $0.00003 $0.00220

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

Security

Grade A, and why

env 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 1mo 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.

Plugins/vercel-marketplace-source/commands/env.md · 264 lines

How it starts

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

Vercel Environment Variables

Manage environment variables for the current Vercel project with safety rails to prevent secret leakage.

🔒 Never-Echo-Secrets Rule: Environment variable values must never appear in command output, summaries, or conversation text. Only show variable names, environments, and metadata (created date, type). This rule applies to all subcommands.

Preflight

  1. CLI available? — Confirm vercel is on PATH.
    • If missing: npm i -g vercel (or pnpm add -g vercel / bun add -g vercel).
  2. Project linked? — Check for .vercel/project.json in the current directory or nearest parent.
    • If not found: run vercel link interactively, then re-run /env.
  3. Detect environment files — Check for .env, .env.local, .env.production.local, .env.development.local in the project root. Note which exist for the diff subcommand.

Plan

Based on "$ARGUMENTS", determine the action:

Argument Action Destructive?
list / ls / (none) List env var names per environment No
pull Download env vars to local .env.local No (overwrites local file)
add <NAME> Add a new env var Yes (if production)
rm <NAME> / remove <NAME> Remove an env var Yes
diff Compare local vs Vercel key names No

For any operation that mutates production environment variables (add or rm targeting production):

⚠️ Production environment mutation requested. This will change environment variables on your live production deployment. Ask the user for explicit confirmation before proceeding. Do not mutate production env vars without a clear "yes."

Commands

"list" or "ls" or no arguments

# List all environment variables
vercel env ls

# Filter by environment
vercel env ls production

Present results as a table of variable names only grouped by environment. Never print values.

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

  1. 1mo ago First seen · 264 lines · 35 tokens per session scan A cb1a0174593e

Subscribe to this mod's changes

env is a command published in the GitHub repository build-with-dhiraj/ai-workflow-framework-portability-kit (5 stars, last pushed 20d ago), licensed MIT. It adds 35 tokens to every session and 2,198 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-09-21.