dev-logs

dev-logs is a command for Claude Code from bybren-llc/safe-agentic-workflow. It costs 8 tokens per session (360 once invoked), scanned A, a copy of check-docker-status, MIT.

A command template for viewing logs from a remote development container, which is an isolated environment running on another machine.

In plain words
What is it for?
Use it to view recent logs, follow new log entries, or display a larger log history through the canonical remote-logs command.
Why use it?
It provides a standard way to inspect what the remote environment is reporting, while noting that the command is deprecated.

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/safe-agentic-workflow/dev-logs
Clone the repo
git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow

Made for: Claude Code.

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 360 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 84% 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.00008 $0.00360
Opus 5 $0.00004 $0.00180
Sonnet 5 $0.00002 $0.00072
Haiku 4.5 $0.00001 $0.00036

Measured 3d ago against content hash 4e046e1231c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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.

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

84% identical to check-docker-status — 17 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 {{TICKET_PREFIX}}-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
{{TICKET_PREFIX}} 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. 3d ago First seen · 43 lines · 0 tokens per session scan A 4e046e1231c6

Subscribe to this mod's changes

dev-logs is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (404 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 360 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to check-docker-status, differing in 17 lines, and is treated as a copy.