dev-logs

dev-logs is a command for Claude Code from bybren-llc/rendertrust. It costs 8 tokens per session (352 once invoked), scanned A, a copy of check-docker-status, Apache-2.0.

A deprecated command alias that forwards to the canonical command for viewing logs from a remote development container. A container is an isolated package used to run an application and its tools.

In plain words
What is it for?
Use the replacement command to view logs, follow new output, or limit the number of displayed lines from the remote container.
Why use it?
It preserves compatibility for users of the old command while directing them to the current remote-logs command.

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/dev-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 dev-logs

README.md
[![agentmods](https://agentmods.dev/badge/commands/bybren-llc/rendertrust/dev-logs.svg)](https://agentmods.dev/commands/bybren-llc/rendertrust/dev-logs)
Your own site
<a href="https://agentmods.dev/commands/bybren-llc/rendertrust/dev-logs"><img src="https://agentmods.dev/badge/commands/bybren-llc/rendertrust/dev-logs.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 352 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 88% 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.1 $0.00008 $0.00352
Opus 5 $0.00004 $0.00176
Sonnet 5 $0.00002 $0.00070
Haiku 4.5 $0.00001 $0.00035

Measured today against content hash ed0acbe5ea0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

dev-logs scanned grade A with 0 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

88% identical to check-docker-status — 21 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/dev-logs.md · 43 lines

What it actually says

📋 TEMPLATE: This command is a template. See "Customization Guide" below to adapt for your infrastructure.

DEPRECATED: This command is an alias to /remote-logs. Use /remote-logs directly.

This command calls /remote-logs which is the canonical command for viewing {{DEV_MACHINE}} container logs.

Usage

/remote-logs
/remote-logs --follow
/remote-logs --tail 500

Why Deprecated?

Per REN-445, we canonicalized around /remote-* and /local-* naming:

  • /remote-* = {{DEV_MACHINE}} operations (staging-first, then dev)
  • /local-* = Local machine operations
  • /remote-logs - Canonical - View {{DEV_MACHINE}} container logs
  • /remote-health - Health dashboard for {{DEV_MACHINE}}
  • /remote-status - Check if {{DEV_MACHINE}} needs update
  • /remote-deploy - Deploy latest image to {{DEV_MACHINE}}

Customization Guide

To adapt this command for your infrastructure, replace these placeholders:

Placeholder Description Example
REN Your Linear ticket prefix WOR, PROJ, TASK
{{DEV_MACHINE}} Your remote dev machine name Pop OS, staging, dev-server
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 · 43 lines · 0 tokens per session scan A ed0acbe5ea0b

Subscribe to this mod's changes

dev-logs 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 352 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to check-docker-status, differing in 21 lines, and is treated as a copy.