Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bybren-llc/a-safe-pulsenpx agentmods add commands/bybren-llc/a-safe-pulse/remote-logsWrote 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/remote-logs)<a href="https://agentmods.dev/commands/bybren-llc/a-safe-pulse/remote-logs"><img src="https://agentmods.dev/badge/commands/bybren-llc/a-safe-pulse/remote-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.00005 | $0.01914 |
| Opus 5 | $0.00003 | $0.00957 |
| Sonnet 5 | $0.00001 | $0.00383 |
| Haiku 4.5 | $0.00001 | $0.00191 |
Grade D, and why
remote-logs scanned grade D with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Provide sudo alternative Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
| `{{SSH_KEY_PATH}}` | Path to SSH private key | `~/.ssh/id_ed25519_staging` | This is a copy
92% identical to remote-logs — 32 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
View logs from the remote development environment containers.
📋 TEMPLATE: This command is a template. Replace placeholders with your infrastructure values before use. See the Customization Guide at the bottom.
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:
# ┌─────────────────────────────────────────────────────────┐
# │ CUSTOMIZE: Replace with your SSH and project settings │
# └─────────────────────────────────────────────────────────┘
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "cd {{PROJECT_PATH}} && ./scripts/dev-docker.sh logs --tail 100"
For specific service:
# Container names - customize for your project
# App logs (dev-mode - STANDARD port 3000)
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker logs {{APP_CONTAINER_DEV}} --tail 100"
# App logs (staging-mode - port 3001)
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker logs {{APP_CONTAINER_STAGING}} --tail 100"
# PostgreSQL logs (staging)
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker logs {{DB_CONTAINER_STAGING}} --tail 100"
# PostgreSQL logs (dev)
ssh -i {{SSH_KEY_PATH}} {{REMOTE_USER}}@{{REMOTE_HOST}} "docker logs {{DB_CONTAINER_DEV}} --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
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Dev Containers (STANDARD port {{DEV_PORT}})
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
{{APP_CONTAINER_DEV}} (Node.js):
Status: ✅ Running
Errors: 0
Warnings: 2
Last Line: [14:35:22] Ready on http://localhost:{{DEV_PORT}}
{{DB_CONTAINER_DEV}}:
Status: ✅ Running
Errors: 0
Last Line: [14:34:10] database system is ready
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Staging Containers (port {{STAGING_PORT}})
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
{{APP_CONTAINER_STAGING}} (Node.js):
Status: ✅ Running
Errors: 0
Warnings: 1
Last Line: [14:35:22] Ready on http://localhost:{{STAGING_PORT}}
Recent warnings:
[14:34:15] WARN: Using development build
[14:34:18] WARN: App not initialized (missing config)
{{DB_CONTAINER_STAGING}}:
Status: ✅ Running
Errors: 0
Last Line: [14:34:10] database system is ready
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Overall Health: ✅ Healthy
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Recommendation: No critical issues detected
Warnings are expected for dev environment
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 · 309 lines · 0 tokens per session scan D 21f706ace684
remote-logs is a command published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 5 tokens to every session and 1,914 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, reaches for credential files). It is 92% identical to remote-logs, differing in 32 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.