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-rollbackgit 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-rollback)<a href="https://agentmods.dev/commands/bybren-llc/rendertrust/remote-rollback"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/remote-rollback.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.02383 |
| Opus 5 | $0.00004 | $0.01192 |
| Sonnet 5 | $0.00002 | $0.00477 |
| Haiku 4.5 | $0.00001 | $0.00238 |
Grade C, and why
remote-rollback 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 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` | 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}}:{{DEV_PORT}}/api/health 2>/dev/null || echo "Health check failed" This is a copy
98% identical to remote-rollback — 12 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rollback the remote development environment to a previous Docker image version.
📋 TEMPLATE: This command is a template. Replace placeholders with your infrastructure values before use. See the Customization Guide at the bottom.
Workflow
1. Assess Current Situation
Get current problematic version:
# ┌─────────────────────────────────────────────────────────┐
# │ CUSTOMIZE: Replace with your SSH and container settings │
# └─────────────────────────────────────────────────────────┘
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker inspect {{APP_CONTAINER_STAGING}} 2>/dev/null | grep 'org.opencontainers.image.revision' | cut -d'\"' -f4 || docker inspect {{APP_CONTAINER_DEV}} | grep 'org.opencontainers.image.revision' | cut -d'\"' -f4"
Check current status:
curl -s http://{{REMOTE_HOST}}:{{DEV_PORT}}/api/health 2>/dev/null || echo "Health check failed"
Document the issue for Linear ticket creation later.
2. List Available Rollback Targets
Show recent images on remote host:
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker images {{REGISTRY}}/{{IMAGE_NAME}} --format 'table {{.Tag}}\t{{.ID}}\t{{.CreatedAt}}'"
Cross-reference with git commits to show messages:
git log origin/dev -10 --oneline
3. Select Rollback Target
If argument provided (commit SHA like e9722d4):
- Use specified commit as rollback target
- Verify image exists with that SHA tag
If no argument provided:
- Display last 5 available images with commit messages
- Recommend previous stable version (before current)
- Ask user to confirm selection
Default behavior: Select image before current (most common rollback scenario)
4. Pull Rollback Image
Pull the specific version from registry:
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker pull {{REGISTRY}}/{{IMAGE_NAME}}:{{TAG_PREFIX}}-{target-sha}"
If image not in registry (old version pruned), use local cached image.
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 · 311 lines · 8 tokens per session scan C 68fc58c11315
remote-rollback is a command published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 2,383 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). It is 98% identical to remote-rollback, differing in 12 lines, and is treated as a copy.
Other commands, from other repositories
create-docker-mcp-tunnel
Stand up an Anthropic MCP tunnel locally with Docker Compose so Claude can call a private MCP server (manual-credentials quickstart).
sandbox
Manage sandbox backends and tooling.
dockerfile
Validate Dockerfiles for GPU/CUDA configuration issues before building.
index
Command "index" from thrashr888/agentkernel, covering commands, quick reference, daily drivers (root level), sandbox lifecycle (sandbox / sb) and ssh (ssh).
deploy
Build, test, deploy with staged rollout.
status
List all SandboxClaims with phase, age, template, and bound pod. Detects stuck-in-Pending claims and surfaces likely causes.