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.
curl -O https://raw.githubusercontent.com/bybren-llc/safe-agentic-workflow/main/.gemini/commands/remote/logs.tomlgit clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflowWrote 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/safe-agentic-workflow/logs)<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>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.00000 | $0.00764 |
| Opus 5 | $0.00000 | $0.00382 |
| Sonnet 5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00076 |
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.
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,errorFATAL,FatalException,exception- Stack traces
Warning Detection:
WARN,Warning,warningdeprecated
Success Markers:
started,listening,readyconnected,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"
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.
- 3d ago First seen · 135 lines · 0 tokens per session scan A 6375938617d4
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.
Other commands, from other repositories
clean
Fix all linting and formatting issues across the codebase.
k8s-debug
Kubernetes debugging commands - troubleshoot pods, services, and cluster issues.
check
Verify code quality, security, performance, and coverage. One command to audit everything.
debug
Comprehensive debugging for Golden Armada agent services.
debug
Apply expert debugging methodology to investigate a specific issue.
workflow-repair
Diagnose and repair corrupted workflow state. Use when state.yaml is invalid, phases are stuck, or domain-memory.yaml has stale locks.