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/local-deploygit 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/local-deploy)<a href="https://agentmods.dev/commands/bybren-llc/rendertrust/local-deploy"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/local-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.02900 |
| Opus 5 | $0.00004 | $0.01450 |
| Sonnet 5 | $0.00002 | $0.00580 |
| Haiku 4.5 | $0.00001 | $0.00290 |
Grade B, and why
local-deploy scanned grade B 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo lsof -i :3000 Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:3000/api/health | jq This is a copy
97% identical to local-deploy — 48 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 — 471 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy the latest Docker image from GitHub Container Registry to your LOCAL machine's Docker. Works on any machine with Docker Desktop or Docker Engine installed.
Usage
/local-deploy # Deploy using dev mode (source-mounted, hot-reload)
/local-deploy --staging # Deploy using staging mode (self-contained, production-like)
/local-deploy --rebuild # Trigger GitHub Actions build first, then deploy
/local-deploy --staging --rebuild # Build and deploy to staging mode
Deployment Modes
| Mode | Flag | Container | Use Case |
|---|---|---|---|
| Development (default) | (none) | rendertrust-dev-app |
Active development with hot-reload (STANDARD port 3000) |
| Staging | --staging |
rendertrust-staging-app |
Production-like, self-contained, survives git operations (port 3001) |
| Both | --both |
Both containers | Run dev and staging simultaneously (REN-400/REN-401) |
When to use each mode:
- Dev mode: You're actively writing code and want hot-reload (STANDARD port 3000)
- Staging mode: Testing, demos, or when you need stability during git operations (port 3001)
- Both modes: Run both simultaneously for testing migrations, feature comparison, etc.
Workflow
1. Parse Arguments
Check flags:
# Check command arguments
if [[ "$*" == *"--staging"* ]]; then
MODE="staging"
else
MODE="development"
fi
if [[ "$*" == *"--rebuild"* ]]; then
REBUILD=true
else
REBUILD=false
fi
2. Pre-Deployment Status Check
Get current running status (check both container types):
# Check for staging container
docker ps --filter name=rendertrust-staging-app --format '{{.Names}}\t{{.Status}}'
# Check for dev container (REN-400: updated container name)
docker ps --filter name=rendertrust-dev-app --format '{{.Names}}\t{{.Status}}'
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 · 471 lines · 8 tokens per session scan B c983d95e2b91
local-deploy 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,900 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). It is 97% identical to local-deploy, differing in 48 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.