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/rendertrust/remote-statusgit clone --depth 1 https://github.com/bybren-llc/rendertrustWrote 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/rendertrust/remote-status)<a href="https://agentmods.dev/commands/bybren-llc/rendertrust/remote-status"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/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.01277 |
| Opus 5 | $0.00003 | $0.00639 |
| Sonnet 5 | $0.00001 | $0.00255 |
| 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 today.
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` | This is a copy
95% identical to remote-status — 6 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.
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 dev
git log origin/dev -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.
- today First seen · 188 lines · 7 tokens per session scan C ef510d3c7d66
remote-status is a command published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 1,277 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). It is 95% identical to remote-status, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.