env-push

A command-line tool that uploads environment variables from a .env file, a text file commonly used to store application configuration.

In plain words
What is it for?
Use it to push variables to one or more named project environments, optionally overwriting values already there.
Why use it?
It avoids entering configuration values one by one when setting up or updating an environment. An option controls whether existing variables are replaced.

Command

Install

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.

agentmods
npx agentmods add commands/gotempsh/temps/env-push
Clone the repo
git clone --depth 1 https://github.com/gotempsh/temps
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 147 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00147
Opus 5 $0.00000 $0.00073
Sonnet 5 $0.00000 $0.00029
Haiku 4.5 $0.00000 $0.00015

Measured 2d ago against content hash 17105320c33a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

env-push 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 2d 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.

skills/temps/references/commands/env-push.md · 18 lines

What it actually says

env:push command reference

Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.

env:push

Push environment variables from a .env file

Options:

Flag Description Default Required
-e, --environment <names> Comma-separated environment names - No
-p, --project <project> Project slug - No
--overwrite Overwrite existing variables - No
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. 2d ago First seen · 18 lines · 0 tokens per session scan A 17105320c33a

Subscribe to this mod's changes

env-push is a command published in the GitHub repository gotempsh/temps (700 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 147 tokens. 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-30.