list-env-vars

list-env-vars is a command for coding agents from atxp-dev/claude. It costs 8 tokens per session (710 once invoked), scanned A, original, MIT.

A command that lists configured environment variables from a production settings file while hiding their values.

In plain words
What is it for?
Use it to inspect the names and count of variables stored in .atxp/.env.production.
Why use it?
It lets developers check which configuration keys exist without exposing secrets such as API keys.

Command

Part of the cloud plugin — 5 commands shipped together

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/atxp-dev/claude/list-env-vars
Clone the repo
git clone --depth 1 https://github.com/atxp-dev/claude

Or install cloud, the plugin that ships this one along with the rest of its 5 commands.

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 list-env-vars

README.md
[![agentmods](https://agentmods.dev/badge/commands/atxp-dev/claude/list-env-vars.svg)](https://agentmods.dev/commands/atxp-dev/claude/list-env-vars)
Your own site
<a href="https://agentmods.dev/commands/atxp-dev/claude/list-env-vars"><img src="https://agentmods.dev/badge/commands/atxp-dev/claude/list-env-vars.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 710 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.00008 $0.00710
Opus 5 $0.00004 $0.00355
Sonnet 5 $0.00002 $0.00142
Haiku 4.5 $0.00001 $0.00071

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

Security

Grade A, and why

list-env-vars 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 3d 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.

cloud/commands/list-env-vars.md · 111 lines

How it starts

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

Lists all environment variables configured in .atxp/.env.production with their values masked for security.

Usage

/list-env-vars

Example Output

Environment variables in .atxp/.env.production:

  GOOGLE_ANALYTICS_API_KEY=ya29...****
  GOOGLE_SEARCH_CONSOLE_KEY=AIza...****
  DATAFORSEO_API_KEY=1234...****

(3 variables configured)

Implementation

#!/bin/bash

ENV_FILE=".atxp/.env.production"

if [ ! -f "$ENV_FILE" ]; then
    echo "No environment variables configured yet."
    echo ""
    echo "To add variables, use:"
    echo "  /configure-env-var KEY VALUE"
    exit 0
fi

# Count non-empty, non-comment lines
VAR_COUNT=$(grep -cE '^[A-Za-z_][A-Za-z0-9_]*=' "$ENV_FILE" 2>/dev/null || echo "0")

if [ "$VAR_COUNT" -eq 0 ]; then
    echo "No environment variables configured yet."
    echo ""
    echo "To add variables, use:"
    echo "  /configure-env-var KEY VALUE"
    exit 0
fi

echo "Environment variables in .atxp/.env.production:"
echo ""

# Read and display each variable with masked value
while IFS= read -r line; do
    # Skip empty lines and comments
    if [ -z "$line" ] || echo "$line" | grep -qE '^\s*#'; then
        continue
    fi

    # Extract key and mask value
    if echo "$line" | grep -qE '^[A-Za-z_][A-Za-z0-9_]*='; then
        KEY=$(echo "$line" | cut -d= -f1)
        VALUE=$(echo "$line" | cut -d= -f2-)

        # Mask the value - show first 4 chars and ****
        if [ ${#VALUE} -le 4 ]; then
            MASKED="****"
        else
            FIRST_CHARS=$(echo "$VALUE" | cut -c1-4)
            MASKED="${FIRST_CHARS}...****"
        fi

        echo "  ${KEY}=${MASKED}"
    fi
done < "$ENV_FILE"

echo ""
echo "(${VAR_COUNT} variable(s) configured)"
echo ""
echo "To modify or add variables, use:"
echo "  /configure-env-var KEY VALUE"
echo ""
echo "To remove a variable, use:"
echo "  /remove-env-var KEY"

Notes

  • Variable values are masked to prevent accidental exposure
  • Only shows the first 4 characters followed by ...****
  • Empty lines and comments are ignored
  • To see actual values, view the .atxp/.env.production file directly

Read the full file on GitHub · 111 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. 3d ago First seen · 111 lines · 8 tokens per session scan A c077b5c92b88

Subscribe to this mod's changes

list-env-vars is a command published in the GitHub repository atxp-dev/claude (2 stars, last pushed 9mo ago), licensed MIT. It adds 8 tokens to every session and 710 once invoked, about $0.0000 per session on Opus 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-08-31.