Borrowing it
Nothing to install: this file belongs to bybren-llc/a-safe-pulse. 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/a-safe-pulse/dev/.gemini/commands/remote/logs.tomlgit clone --depth 1 https://github.com/bybren-llc/a-safe-pulseWrote 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/a-safe-pulse/logs)<a href="https://agentmods.dev/commands/bybren-llc/a-safe-pulse/logs"><img src="https://agentmods.dev/badge/commands/bybren-llc/a-safe-pulse/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.00703 |
| Opus 5 | $0.00000 | $0.00351 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00070 |
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 2d 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.
This is a copy
100% identical to logs — 9 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.
How it starts
The opening of the file, as written. The whole thing — 128 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"
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} (Node.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
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"
6. Log Search
Search for specific term:
ssh -i {SSH_KEY_PATH} {REMOTE_USER}@{REMOTE_HOST} "docker logs {APP_CONTAINER} 2>&1 | grep -i 'search-term'"
Usage Examples
/remote:logs # Show last 100 lines from all containers
/remote:logs --follow # Streams logs continuously
/remote:logs --tail 500 # Shows last 500 lines
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.
- 2d ago First seen · 128 lines · 0 tokens per session scan A 94ee2834358c
logs is a command published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 703 tokens. A static security scan graded it A with 0 findings. It is 100% identical to logs, differing in 9 lines, and is treated as a copy.
Other commands, from other repositories
runtime-logs
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
ci-fix
Fix CI pipeline issues with interactive approval.
debug
Structured platform troubleshooting — classifies the problem layer, collects evidence, forms a root-cause hypothesis, and proposes a fix with validation and rollback steps.
k8s-debug
Kubernetes debugging commands - troubleshoot pods, services, and cluster issues.
debug
Comprehensive debugging for Golden Armada agent services.