remote-logs

remote-logs is a command for Claude Code from bybren-llc/rendertrust. It costs 5 tokens per session (2,175 once invoked), scanned D, a copy of remote-logs, Apache-2.0.

View remote dev container logs.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/bybren-llc/rendertrust/remote-logs
Clone the repo
git clone --depth 1 https://github.com/bybren-llc/rendertrust

Made for: Claude Code.

Wrote 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.

agentmods badge for remote-logs

README.md
[![agentmods](https://agentmods.dev/badge/commands/bybren-llc/rendertrust/remote-logs.svg)](https://agentmods.dev/commands/bybren-llc/rendertrust/remote-logs)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,175 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00005 $0.02175
Opus 5 $0.00003 $0.01087
Sonnet 5 $0.00001 $0.00435
Haiku 4.5 $0.00001 $0.00217

Measured today against content hash 1adbf00f957a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

- 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` |
Origin

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.

.claude/commands/remote-logs.md · 331 lines

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, error
  • FATAL, Fatal
  • Exception, exception
  • Stack traces

Warning Detection:

Read the full file on GitHub · 331 lines

Changes

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.

  1. today First seen · 331 lines · 0 tokens per session scan D 1adbf00f957a

Subscribe to this mod's changes

remote-logs is a command published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo 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. 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.