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-statusgit 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-status)<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/remote-status"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/remote-status.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.00007 | $0.01285 |
| Opus 5 | $0.00003 | $0.00642 |
| Sonnet 5 | $0.00001 | $0.00257 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade C, and why
remote-status scanned grade C 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 5d 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_KEY_PATH}}` | Path to SSH private key | `~/.ssh/id_ed25519_staging` | Copies of this mod
2 near-identical copies found in the catalogue:
- remote-status — 95% identical, 6 lines differ
- remote-status — 95% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remote Status Command
Compare the Docker image running on your remote host with the latest image in the registry.
📋 TEMPLATE: This command is a template. See "Customization Guide" below to adapt for your infrastructure.
Deployment Modes
Most Docker setups support two deployment modes:
| Mode | Container Name | Port | Use Case |
|---|---|---|---|
| Development | {{PROJECT}}-dev |
3000 |
Hot-reload, source-mounted, local dev tools |
| Staging | {{PROJECT}}-staging |
3001 |
Production-like, self-contained, stable |
Dev mode uses standard ports so local tools work by default.
Staging mode is recommended - it's stable and won't break during git pull.
Workflow
1. Get Running Container Info
Check running container on remote host:
# ┌─────────────────────────────────────────────────────────────────────┐
# │ CUSTOMIZE: Replace with your SSH and container details │
# └─────────────────────────────────────────────────────────────────────┘
# Check dev container
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} \
"docker ps --filter name={{PROJECT}}-dev --format 'table {{.Names}}\t{{.Image}}\t{{.Status}}'"
# Check staging container
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} \
"docker ps --filter name={{PROJECT}}-staging --format 'table {{.Names}}\t{{.Image}}\t{{.Status}}'"
Extract commit SHA from running container:
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} \
"docker inspect {{CONTAINER_NAME}} | grep 'org.opencontainers.image.revision'"
Get image creation time:
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} \
"docker images {{REGISTRY}}:latest --format '{{.CreatedAt}}'"
2. Get Latest Registry Image Info
Check latest commit on your main branch:
git fetch origin {{MAIN_BRANCH}}
git log origin/{{MAIN_BRANCH}} -1 --format='%H %s'
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.
- 5d ago First seen · 188 lines · 7 tokens per session scan C 63481207ffc8
remote-status is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 1,285 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
deployment
Basic production deployment setup for FastAPI applications.
dare-docker-compose
Este comando analisa a arquitetura definida no BLUEPRINT.md e gera um docker-compose.yml completo com todos os serviços necessários (App, DB, Cache, etc).
dare-dockerfile
Este comando analisa a stack do projeto (definida no DESIGN.md ou .cursorrules) e gera um Dockerfile otimizado para produção e desenvolvimento.
dare-docker
Containerização DARE com Dockerfile e docker-compose seguros, performantes e idiomáticos. Multi-stage, usuário não-root, healthchecks, redes isoladas.
secure-flow-harden-dockerfile-fips
Transform your Docker images to FIPS compliant by removing root users and ensuring security best practices. Make all production docker images in this repository FIPS compliant by hardening Dockerfiles and ensuring they do not run as root users.
sandbox
Manage sandbox backends and tooling.