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.
npx agentmods add commands/atxp-dev/claude/configure-env-vargit clone --depth 1 https://github.com/atxp-dev/claudeWrote 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.
[](https://agentmods.dev/commands/atxp-dev/claude/configure-env-var)<a href="https://agentmods.dev/commands/atxp-dev/claude/configure-env-var"><img src="https://agentmods.dev/badge/commands/atxp-dev/claude/configure-env-var.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00012 | $0.01282 |
| Opus 5 | $0.00006 | $0.00641 |
| Sonnet 5 | $0.00002 | $0.00256 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade B, and why
configure-env-var scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 "$ENV_FILE" How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sets an environment variable by writing it to .atxp/.env.production, which is included in deployments to cloud.atxp.ai.
Usage
/configure-env-var KEY VALUE
Replace KEY with your environment variable name and VALUE with its value.
Examples
Set API keys for external services:
/configure-env-var GOOGLE_ANALYTICS_API_KEY ya29.a0AfH6SMBx...
/configure-env-var GOOGLE_SEARCH_CONSOLE_KEY AIzaSyC...
/configure-env-var DATAFORSEO_API_KEY 12345678-1234-1234-1234-123456789abc
How it works
- Creates
.atxp/.env.productionif it doesn't exist - Adds or updates the environment variable in
KEY=VALUEformat - Sets file permissions to
600(owner read/write only) - The file will be included in your next
/deploy - Your deployed agent can access these variables at runtime
Requirements
- Bash 3.2+ (default on macOS and most Linux distributions)
- Write access to current directory
Value Handling
- Empty values: Not allowed. Use
/remove-env-varto delete variables. - Values with spaces: Fully supported (e.g.,
"Hello World") - Values with special characters: Supported including
=,:,/, etc. - Multiline values: Not supported. Use base64 encoding if needed.
Implementation
#!/bin/bash
# Parse arguments
if [ "$#" -lt 2 ]; then
echo "Usage: /configure-env-var KEY VALUE"
echo "Example: /configure-env-var API_KEY abc123"
exit 1
fi
KEY="$1"
shift
VALUE="$*"
# Validate key format (alphanumeric and underscore only)
if ! echo "$KEY" | grep -qE '^[A-Za-z_][A-Za-z0-9_]*$'; then
echo "Error: KEY must start with a letter or underscore and contain only alphanumeric characters and underscores"
exit 1
fi
# Create .atxp directory if it doesn't exist
mkdir -p .atxp
ENV_FILE=".atxp/.env.production"
# Create or update the env file
if [ -f "$ENV_FILE" ]; then
# File exists, check if key already exists
if grep -q "^${KEY}=" "$ENV_FILE"; then
# Update existing key
# Use a temporary file for safety
TEMP_FILE=$(mktemp) || {
echo "Error: Failed to create temporary file"
exit 1
}
while IFS= read -r line; do
if [[ "$line" =~ ^${KEY}= ]]; then
echo "${KEY}=${VALUE}"
else
echo "$line"
fi
done < "$ENV_FILE" > "$TEMP_FILE"
mv "$TEMP_FILE" "$ENV_FILE"
echo "✓ Updated ${KEY} in ${ENV_FILE}"
else
# Append new key
echo "${KEY}=${VALUE}" >> "$ENV_FILE"
echo "✓ Added ${KEY} to ${ENV_FILE}"
fi
else
# Create new file
echo "${KEY}=${VALUE}" > "$ENV_FILE"
chmod 600 "$ENV_FILE"
echo "✓ Created ${ENV_FILE} with ${KEY}"
fi
# Ensure restrictive permissions on existing file
chmod 600 "$ENV_FILE" 2>/dev/null || true
# Check if .gitignore exists and contains the env file
GITIGNORE_WARNED=false
if [ -f ".gitignore" ]; then
if ! grep -qF ".atxp/.env.production" .gitignore; then
GITIGNORE_WARNED=true
fi
else
GITIGNORE_WARNED=true
fi
if [ "$GITIGNORE_WARNED" = true ]; then
echo ""
echo "⚠️ SECURITY WARNING: Add .atxp/.env.production to your .gitignore"
echo " Run: echo '.atxp/.env.production' >> .gitignore"
fi
echo ""
echo "Next steps:"
echo " 1. Review variables: /list-env-vars"
echo " 2. Deploy your agent: /deploy"
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.
- 3d ago First seen · 169 lines · 12 tokens per session scan B c234e86e706e
configure-env-var is a command published in the GitHub repository atxp-dev/claude (2 stars, last pushed 9mo ago), licensed MIT. It adds 12 tokens to every session and 1,282 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.