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.
npx skills add anatolykoptev/dozor --skill remote-servergit clone --depth 1 https://github.com/anatolykoptev/dozorWrote 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/skills/anatolykoptev/dozor/remote-server)<a href="https://agentmods.dev/skills/anatolykoptev/dozor/remote-server"><img src="https://agentmods.dev/badge/skills/anatolykoptev/dozor/remote-server.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.00045 | $0.00784 |
| Opus 5 | $0.00023 | $0.00392 |
| Sonnet 5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
remote-server 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remote Server
Manage a remote server via SSH. All operations use server_remote and server_inspect tools.
Services
| Service | Role | Port |
|---|---|---|
| nginx | Web server / reverse proxy | 80, 443 |
| php-fpm | PHP application server | 9000 (unix socket) |
| database (mariadb/mysql) | Database | 3306 |
| redis | Cache | 6379 |
Quick Status
server_inspect(mode: "remote")
Returns: HTTP status, SSL expiry, all service states, disk/memory/load.
Troubleshooting Flows
Site Unreachable (HTTP down)
1. server_inspect(mode: "remote") — confirm HTTP fail + check all services
2. If nginx down:
server_remote(action: "restart", service: "nginx")
3. If PHP down:
server_remote(action: "restart", service: "php-fpm")
4. If both up but HTTP fails:
server_remote(action: "logs", service: "nginx", lines: 100)
-> Look for upstream errors, config issues
5. If DB down:
Restart in order: database -> redis -> php-fpm -> nginx
6. Verify: server_inspect(mode: "remote")
Service Down
1. server_remote(action: "status") — confirm which service
2. server_remote(action: "logs", service: NAME, lines: 50) — check why
3. server_remote(action: "restart", service: NAME) — restart
4. server_remote(action: "status") — verify recovery
5. If still down after 2 attempts: escalate with log excerpt
SSL Certificate Expiring
1. server_inspect(mode: "remote") — check SSL expiry
2. If < 7 days: escalate immediately (P0)
3. If < 14 days: report as P1 warning
4. Renewal is handled externally (Let's Encrypt / hosting panel)
High Load on Remote
1. Use server_remote_exec tool with "top -bn1 | head -20"
2. Check if PHP-FPM workers (traffic spike) or DB queries
3. If PHP-FPM: check for stuck processes
server_remote(action: "logs", service: "php-fpm", lines: 100)
4. If database: check slow queries
server_remote(action: "logs", service: "database", lines: 100)
Disk Full on Remote
1. Use server_remote_exec tool with "df -h"
2. Check application debug.log size
3. If debug.log large: truncate or rotate
4. Check nginx access logs
5. Escalate if not enough to free
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.
- 8d ago First seen · 100 lines · 45 tokens per session scan A 4f5184fc54ee
remote-server is a skill published in the GitHub repository anatolykoptev/dozor (5 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 784 once invoked, about $0.0002 per session on Opus 5. 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-08-31.
Other skills, from other repositories
System Healthcheck
Run a lightweight, non-destructive system healthcheck — disk usage, memory, CPU load, process count, hostname — and store a structured snapshot in session memory. Use when the user says "run a healthcheck", "check system health", "how's the server doing", "is everything ok", or asks for a status/diagnostics snapshot…
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
stack-trace-go-probe
Internal helper for meta-stack-trace-investigator. Use when a Go panic or stack trace needs Go-specific nil/error checks, go test reproducer guidance, and patch targets.
stack-trace-python-probe
Internal helper for meta-stack-trace-investigator. Use when a Python traceback needs Python-specific root-cause checks, pytest reproducer guidance, and defensive patch targets.
stack-trace-rust-probe
Internal helper for meta-stack-trace-investigator. Use when a Rust panic or backtrace needs Rust-specific Result/Option checks, cargo test guidance, and patch targets.