Borrowing it
Nothing to install: this file belongs to bybren-llc/rendertrust. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bybren-llc/rendertrust/dev/.claude/commands/remote-logs.mdgit 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-logs)<a href="https://agentmods.dev/commands/bybren-llc/rendertrust/remote-logs"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/remote-logs/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/rendertrust/remote-logs"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/remote-logs.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.00005 | $0.02175 |
| Opus 5.5 | $0.00002 | $0.00870 |
| Sonnet 5.5 | $0.00001 | $0.00435 |
| Haiku 4.5 | $0.00001 | $0.00217 |
Grade D, and why
remote-logs scanned grade D 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 1mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Provide sudo alternative 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
100% identical to remote-logs — 0 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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
View logs from the remote development environment containers.
📋 TEMPLATE: This command is a template. Replace placeholders with your infrastructure values before use. See the Customization Guide at the bottom.
Workflow
1. Determine Log Mode
If argument contains --follow or -f:
- Stream logs in real-time
- Useful for monitoring deployments
- Press Ctrl+C to exit
If argument contains --tail N:
- Show last N lines
- Default to 100 if not specified
If no arguments:
- Show last 100 lines (default)
2. Execute Log Command
Get logs from all services:
# ┌─────────────────────────────────────────────────────────┐
# │ CUSTOMIZE: Replace with your SSH and project settings │
# └─────────────────────────────────────────────────────────┘
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "cd {{PROJECT_PATH}} && ./scripts/dev-docker.sh logs --tail 100"
For specific service:
# Container names - customize for your project
# App logs (dev-mode - STANDARD port 3000)
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker logs {{APP_CONTAINER_DEV}} --tail 100"
# App logs (staging-mode - port 3001)
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker logs {{APP_CONTAINER_STAGING}} --tail 100"
# PostgreSQL logs (staging)
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker logs {{DB_CONTAINER_STAGING}} --tail 100"
# PostgreSQL logs (dev)
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker logs {{DB_CONTAINER_DEV}} --tail 100"
# Redis logs (staging)
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker logs {{REDIS_CONTAINER_STAGING}} --tail 100"
# Redis logs (dev)
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker logs {{REDIS_CONTAINER_DEV}} --tail 100"
3. Filter and Highlight
Parse logs for common patterns:
Error Detection:
ERROR,Error,errorFATAL,FatalException,exception- Stack traces
Warning Detection:
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.
- 1mo ago First seen · 331 lines · 0 tokens per session scan D 1adbf00f957a
remote-logs is a command published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 5 tokens to every session and 2,175 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it D with 2 findings (asks for root, reaches for credential files). It is 100% identical to remote-logs, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
runtime-logs
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
k8s-troubleshoot
Diagnose a misbehaving Kubernetes workload using MCP tools.
k8s-debug
Kubernetes debugging commands - troubleshoot pods, services, and cluster issues.
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
ci-fix
Fix CI pipeline issues with interactive approval.
debug
Comprehensive debugging for Golden Armada agent services.