remote-deploy

remote-deploy is a command for Claude Code from bybren-llc/a-safe-pulse. It costs 8 tokens per session (875 once invoked), scanned C, a copy of remote-deploy, MIT.

A command template for deploying the latest Docker image to a remote staging environment. It connects over SSH, runs a deployment script, and is intended to pull and start the updated image.

In plain words
What is it for?
Use it to run a staging deployment with your SSH key, server, project path, and deployment script.
Why use it?
It gives a repeatable way to update a remote staging server instead of carrying out each deployment step manually. The placeholders must be adapted to your infrastructure.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is # ssh -i ~/.ssh/id_ed25519_staging [email protected] "cd ~/app && ./scripts/deploy.sh".

Good fit Use it to run a staging deployment with your SSH key, server, project path, and deployment script.

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/bybren-llc/a-safe-pulse
agentmods
npx agentmods add commands/bybren-llc/a-safe-pulse/remote-deploy

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/bybren-llc/a-safe-pulse/remote-deploy/github.svg)](https://agentmods.dev/commands/bybren-llc/a-safe-pulse/remote-deploy)
Your own site
<a href="https://agentmods.dev/commands/bybren-llc/a-safe-pulse/remote-deploy"><img src="https://agentmods.dev/badge/commands/bybren-llc/a-safe-pulse/remote-deploy/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 remote-deploy

Your own site · 80×15
<a href="https://agentmods.dev/commands/bybren-llc/a-safe-pulse/remote-deploy"><img src="https://agentmods.dev/badge/commands/bybren-llc/a-safe-pulse/remote-deploy.svg" alt="Reviewed on agentmods" width="80" 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 875 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00008 $0.00875
Opus 5.5 $0.00003 $0.00350
Sonnet 5.5 $0.00002 $0.00175
Haiku 4.5 $0.00001 $0.00088

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

Security

Grade C, and why

remote-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 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.

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.

# ssh -i ~/.ssh/id_ed25519_staging [email protected] "cd ~/app && ./scripts/deploy.sh"

Makes network callslowCapability

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

curl -s http://{{REMOTE_HOST}}:{{STAGING_PORT}}/api/health | jq
Origin

This is a copy

100% identical to remote-deploy — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/remote-deploy.md · 113 lines

How it starts

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

Remote Deploy Command

Deploy the latest Docker image to your remote staging environment.

📋 TEMPLATE: This command is a template. See "Customization Guide" below to adapt for your infrastructure.

Quick Deploy Command

Execute single deploy command on remote host:

# ┌─────────────────────────────────────────────────────────────────────┐
# │ CUSTOMIZE: Replace with your SSH connection details                  │
# │ - SSH_KEY_PATH: Path to your SSH private key                        │
# │ - REMOTE_USER: Your username on the remote host                     │
# │ - REMOTE_HOST: Hostname or IP of your staging server                │
# │ - PROJECT_PATH: Path to your project on the remote host             │
# │ - DEPLOY_SCRIPT: Your deployment script path                        │
# └─────────────────────────────────────────────────────────────────────┘
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "cd {{PROJECT_PATH}} && {{DEPLOY_SCRIPT}}"

# Example with real values:
# ssh -i ~/.ssh/id_ed25519_staging [email protected] "cd ~/app && ./scripts/deploy.sh"

This command should handle:

  1. Pull latest image from container registry
  2. Start staging compose (no source mounts)
  3. Wait for health check
  4. Report status with container revision

Expected output on success:

Deploying to staging environment...
Pulling latest image...
Starting staging services...
Waiting for health check...
Deploy complete!
Status: Up 5 seconds (health: starting)
Revision: abc1234
URL: http://localhost:{{STAGING_PORT}}

Expected duration: 2-5 minutes

Success Criteria

  • Container running (healthy)
  • Health endpoint returns 200
  • Image revision matches latest commit

Error Handling

Pull Failed

Possible causes:

  • Registry auth expired - run docker login {{REGISTRY}}
  • Disk space full - run df -h on remote host

Health Check Failed

The deploy script should show recent logs. Common actions:

  • Check logs for startup errors
  • Verify database connection
  • Run /remote-rollback to restore previous working state

Read the full file on GitHub · 113 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 · 113 lines · 8 tokens per session scan C 7d121f1fdaaf

Subscribe to this mod's changes

remote-deploy is a command published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 875 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). It is 100% identical to remote-deploy, differing in 0 lines, and is treated as a copy.