safe-agentic-workflow: Command for Gemini CLI

.gemini/commands/remote/logs.toml

logs is a command for Gemini CLI from bybren-llc/safe-agentic-workflow. It costs 0 tokens per session (764 once invoked), scanned A, original, MIT.

A command for viewing logs from containers in a remote development environment. Logs are records of messages and errors produced by running services.

In plain words
What is it for?
Use it to view logs from all services or from a specific application, PostgreSQL, or Redis container, with optional line limits or live streaming.
Why use it?
It makes remote service problems easier to inspect without opening each container manually. It can show recent output, follow new messages in real time, and highlight common errors.

Command for Gemini CLI

Written for Gemini CLI: installed under .gemini/.

This is bybren-llc/safe-agentic-workflow's own configuration. It tells Gemini CLI how to work on safe-agentic-workflow itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything safe-agentic-workflow configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ssh -i {SSH_KEY_PATH} {REMOTE_USER}@{REMOTE_HOST} "cd {PROJECT_PATH} && ./scripts/dev-docker.sh logs --tail 100".

Reuse

Borrowing it

Nothing to install: this file belongs to bybren-llc/safe-agentic-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/bybren-llc/safe-agentic-workflow/main/.gemini/commands/remote/logs.toml
Clone the repo
git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow

Made for: Gemini CLI.

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 logs

README.md
[![agentmods](https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/logs.svg)](https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/logs)
Your own site
<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/logs"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/logs.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 764 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00000 $0.00764
Opus 5 $0.00000 $0.00382
Sonnet 5 $0.00000 $0.00153
Haiku 4.5 $0.00000 $0.00076

Measured 3d ago against content hash 6375938617d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

Copies of this mod

2 near-identical copies found in the catalogue:

  • logs — 100% identical, 0 lines differ
  • logs — 100% identical, 9 lines differ
.gemini/commands/remote/logs.toml · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

description = "View remote dev container logs"

prompt = """

Remote Logs Command

View logs from the remote development environment containers.

Arguments: {{args}}

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:

ssh -i {SSH_KEY_PATH} {REMOTE_USER}@{REMOTE_HOST} "cd {PROJECT_PATH} && ./scripts/dev-docker.sh logs --tail 100"

For specific service:

# App logs
ssh -i {SSH_KEY_PATH} {REMOTE_USER}@{REMOTE_HOST} "docker logs {APP_CONTAINER} --tail 100"

# PostgreSQL logs
ssh -i {SSH_KEY_PATH} {REMOTE_USER}@{REMOTE_HOST} "docker logs {DB_CONTAINER} --tail 100"

# Redis logs
ssh -i {SSH_KEY_PATH} {REMOTE_USER}@{REMOTE_HOST} "docker logs {REDIS_CONTAINER} --tail 100"

3. Filter and Highlight

Parse logs for common patterns:

Error Detection:

  • ERROR, Error, error
  • FATAL, Fatal
  • Exception, exception
  • Stack traces

Warning Detection:

  • WARN, Warning, warning
  • deprecated

Success Markers:

  • started, listening, ready
  • connected, successful

Highlight critical issues in output.

4. Log Analysis

Provide quick analysis:

Remote Dev Logs Analysis

{APP_CONTAINER} (Next.js):
  Status:    Running
  Errors:    0
  Warnings:  2
  Last Line: Ready on http://localhost:3000

{DB_CONTAINER}:
  Status:    Running
  Errors:    0
  Last Line: database system is ready

{REDIS_CONTAINER}:
  Status:    Running
  Errors:    0
  Last Line: Ready to accept connections

Overall Health: Healthy

5. Interactive Follow Mode

If --follow requested, start streaming:

ssh -i {SSH_KEY_PATH} {REMOTE_USER}@{REMOTE_HOST} "cd {PROJECT_PATH} && ./scripts/dev-docker.sh logs --follow"

Read the full file on GitHub · 135 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. 3d ago First seen · 135 lines · 0 tokens per session scan A 6375938617d4

Subscribe to this mod's changes

logs is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 764 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.