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.
git 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-health)<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/remote-health"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/remote-health/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.
<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/remote-health"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/remote-health.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00006 | $0.01497 |
| Opus 5 | $0.00003 | $0.00749 |
| Sonnet 5 | $0.00001 | $0.00299 |
| Haiku 4.5 | $0.00001 | $0.00150 |
Grade C, and why
remote-health 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 9d 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` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -w '\nHTTP Status: %{http_code}\nResponse Time: %{time_total}s\n' \ Copies of this mod
2 near-identical copies found in the catalogue:
- remote-health — 98% identical, 6 lines differ
- remote-health — 92% identical, 20 lines differ
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remote Health Command
Display comprehensive health status of your remote dev environment including containers, resources, connectivity, and recent issues.
📋 TEMPLATE: This command is a template. See "Customization Guide" at the end to adapt for your infrastructure.
Workflow
1. Container Health Check
Check all project services:
# ┌─────────────────────────────────────────────────────────────────────┐
# │ CUSTOMIZE: Replace with your SSH and container details │
# └─────────────────────────────────────────────────────────────────────┘
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} \
"docker ps --filter name={{PROJECT}} --format 'table {{.Names}}\t{{.Status}}\t{{.State}}'"
Get detailed health status:
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} \
"docker inspect {{CONTAINER_NAME}} --format='{{.Name}}: {{.State.Health.Status}}'"
2. Resource Usage
Check CPU and Memory usage:
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} \
"docker stats --no-stream --format 'table {{.Name}}\t{{.CPUPerc}}\t{{.MemUsage}}'"
Check disk space:
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "df -h / | tail -1"
Check Docker disk usage:
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker system df"
3. Application Health Endpoint
Test your app's health endpoint:
# ┌─────────────────────────────────────────────────────────────────────┐
# │ CUSTOMIZE: Replace with your health endpoint URL │
# └─────────────────────────────────────────────────────────────────────┘
curl -s -w '\nHTTP Status: %{http_code}\nResponse Time: %{time_total}s\n' \
http://{{REMOTE_HOST}}:{{APP_PORT}}/api/health
Expected response:
{
"status": "healthy",
"timestamp": "2025-10-11T19:35:00.000Z",
"uptime": 25234.567,
"environment": "development"
}
4. Database Connectivity
Test PostgreSQL connection:
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.
- 9d ago First seen · 207 lines · 6 tokens per session scan C b579c2ffee53
remote-health is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 1,497 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
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.
application-crud
A command reference for creating and managing Coolify applications connected to private GitHub repositories. It covers application records, deployment settings, and common API errors.