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/bybren-llc/safe-agentic-workflow/remote-deploygit clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflowWrote 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/bybren-llc/safe-agentic-workflow/remote-deploy)<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/remote-deploy"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/remote-deploy.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.00008 | $0.00875 |
| Opus 5 | $0.00004 | $0.00438 |
| Sonnet 5 | $0.00002 | $0.00175 |
| Haiku 4.5 | $0.00001 | $0.00088 |
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 4d 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 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:
- Pull latest image from container registry
- Start staging compose (no source mounts)
- Wait for health check
- 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 -hon remote host
Health Check Failed
The deploy script should show recent logs. Common actions:
- Check logs for startup errors
- Verify database connection
- Run
/remote-rollbackto restore previous working state
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.
- 4d ago First seen · 113 lines · 8 tokens per session scan C 7d121f1fdaaf
remote-deploy is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 875 once invoked, about $0.0000 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-30.
Other commands, from other repositories
help
Category: System Syntax: /help [command|topic].
translate-docs
翻译项目文档到指定语言.
review-tasks
审查任务的忠实度、可执行性、依赖关系与验证.
clarify
Reduce spec ambiguity via targeted questions with adaptive auto-invocation (planning is 80% of success).
tasks-to-issues
将现有任务转换为该功能的可操作 GitHub Issues.
ultrathink
Enter deep craftsman mode - question everything, plan like Da Vinci, craft insanely great solutions, then materialize to roadmap.