A command that packages the current working directory and deploys it as a Claude agent to cloud.atxp.ai.

Use it to deploy the project when the required ATXP connection setting and command-line tools are available.

It moves the current project into a hosted agent environment instead of leaving it only on the local machine.

deploy — Command by atxp-dev

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/deploy

Clone the repo

git clone --depth 1 https://github.com/atxp-dev/claude

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,883 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 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.

Model	Per session	Once invoked
Fable 5	$0.00016	$0.01883
Opus 5	$0.00008	$0.00941
Sonnet 5	$0.00003	$0.00377
Haiku 4.5	$0.00002	$0.00188

Measured yesterday against content hash 86a08b86d93d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

deploy scanned grade C with 2 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 yesterday.

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.

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

-x ".netrc" \

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- `curl` and `jq` must be available in your PATH

cloud/commands/deploy.md · 254 lines

How it starts

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

Deploy Command

This command packages and deploys the current working directory to cloud.atxp.ai.

Prerequisites

ATXP_CONNECTION_STRING environment variable must be set with your ATXP connection URL
The connection string should contain a connection_token query parameter
curl and jq must be available in your PATH

IMPORTANT: When this command is complete, share the uploaded instance URL with the user! The URL is in this format: https://cloud.atxp.ai/${instanceId}.

Steps

1. Extract the connection token from ATXP_CONNECTION_STRING

The connection token is a query parameter in the connection URL:

# Extract connection_token from the URL
CONNECTION_TOKEN=$(echo "$ATXP_CONNECTION_STRING" | grep -o 'connection_token=[^&]*' | cut -d= -f2)

if [ -z "$CONNECTION_TOKEN" ]; then
  echo "Error: Could not extract connection_token from ATXP_CONNECTION_STRING"
  exit 1
fi

2. Create a zip file of the current directory

# Create a temporary zip file (using mktemp for security)
TEMP_BASE=$(mktemp /tmp/deploy-XXXXXX)
ZIP_FILE="${TEMP_BASE}.zip"
rm "$TEMP_BASE"  # Remove the temporary placeholder
echo "Creating deployment package..."

# Zip the current directory, excluding common files and sensitive data
zip -r "$ZIP_FILE" . \
  -x ".git/*" \
  -x "node_modules/*" \
  -x "*/node_modules/*" \
  -x ".atxp-instance" \
  -x ".DS_Store" \
  -x "*/.DS_Store" \
  -x ".env.local" \
  -x ".env.*.local" \
  -x "*/.env.local" \
  -x "*/.env.*.local" \
  -x ".env.development" \
  -x "*/.env.development" \
  -x ".env.test" \
  -x "*/.env.test" \
  -x ".npmrc" \
  -x "*/.npmrc" \
  -x ".netrc" \
  -x "*/.netrc" \
  -x ".aws/*" \
  -x "*/.aws/*" \
  -x "*.pem" \
  -x "*.key" \
  -x "*.p12" \
  -x "*.pfx" \
  > /dev/null

echo "Package created: $(du -h "$ZIP_FILE" | cut -f1)"

3. Check for existing instance ID

The instance ID is stored in .atxp-instance in the current directory:

INSTANCE_FILE=".atxp-instance"
INSTANCE_ID=""

if [ -f "$INSTANCE_FILE" ]; then
  INSTANCE_ID=$(cat "$INSTANCE_FILE")
  echo "Found existing instance: $INSTANCE_ID"
fi

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

yesterday First seen · 254 lines · 16 tokens per session scan C 86a08b86d93d

Subscribe to this mod's changes

deploy is a command published in the GitHub repository atxp-dev/claude (2 stars, last pushed 9mo ago), licensed MIT. It adds 16 tokens to every session and 1,883 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

DevOps and cloud

deploy

Getting it into your agent

What it costs to keep this loaded

Grade C, and why

Reaches for credential fileshighPrivilege escalation

Makes network callslowCapability

How it starts

Deploy Command

Prerequisites

Steps

1. Extract the connection token from ATXP_CONNECTION_STRING

2. Create a zip file of the current directory

3. Check for existing instance ID

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement