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 incident-responsegit 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/incident-response)<a href="https://agentmods.dev/skills/anatolykoptev/dozor/incident-response"><img src="https://agentmods.dev/badge/skills/anatolykoptev/dozor/incident-response/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/anatolykoptev/dozor/incident-response"><img src="https://agentmods.dev/badge/skills/anatolykoptev/dozor/incident-response.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.01130 |
| Opus 5 | $0.00018 | $0.00565 |
| Sonnet 5 | $0.00007 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
incident-response 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 12d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response
Classify severity, respond accordingly, and track resolution.
Severity Levels
| Level | Meaning | Response Time | Auto-fix? |
|---|---|---|---|
| P0 CRITICAL | Service outage, data at risk, user-facing down | Immediate | Yes — restart, then verify |
| P1 WARNING | Degraded performance, threshold breach, unhealthy | Within minutes | Yes — targeted fix |
| P2 INFO | Minor anomaly, cosmetic, scheduled maintenance | Report only | No — inform user |
Classification Rules
P0 CRITICAL:
- Any container in
exitedorrestartingstate - Disk usage > 95%
- User-facing HTTP endpoint unreachable
- Database (postgres/mysql/mariadb) down
- OOM kill detected in logs
P1 WARNING:
- Disk usage 80-95%
- Memory usage > 90%
- CPU load > 2x core count for > 5 min
- Error rate > 5 errors/min in any service
- SSL certificate expires in < 14 days
- Container restart count > 3
P2 INFO:
- Disk usage 60-80%
- Service uptime < 1 hour (recent restart)
- Non-critical container unhealthy
- Pending system updates
Response Flow
1. CLASSIFY — determine severity from triage/alert data
2. ACT (P0/P1):
a. For P0: restart affected service immediately
b. For P1: diagnose first (read_skill: diagnostics), then fix
c. Verify fix: re-run server_inspect(mode: "health")
3. ESCALATE if:
- Same service fails 3+ times
- Fix requires code changes
- Multiple P0 issues simultaneously (read_skill: escalation)
4. RECORD — update_memory with incident details
5. NOTIFY — response goes to Telegram via bus
Auto-Fix Actions (Safe)
These actions are safe to take without human approval:
| Issue | Auto-fix |
|---|---|
| Container down | server_restart(service: NAME) |
| Systemd service down | server_services(action: "restart", service: NAME) |
| Remote service down | server_remote(action: "restart", service: NAME) |
| Disk > 90% | server_cleanup(targets: ["journal", "docker", "tmp"], report: false, min_age: "7d") |
| Docker build cache bloat | server_prune(age: "48h") |
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.
- 12d ago First seen · 132 lines · 36 tokens per session scan A 5372c96a82b6
incident-response is a skill published in the GitHub repository anatolykoptev/dozor (5 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,130 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
run-llms
Comprehensive guide for setting up and running local LLMs using Harbor. Use when user wants to run LLMs locally, set up or troubleshoot Ollama, Open WebUI, llama.cpp, vLLM, SearXNG, Open Terminal, or similar local AI services. Covers full setup from Docker prerequisites through running models, per-service…
harbor
CLI toolkit for managing containerized LLM services. Use when the user wants to start, stop, configure, or manage AI/LLM services like Ollama, Open WebUI, llama.cpp, vLLM, LiteLLM, ComfyUI, and 250+ others. Triggers on requests to "run a model", "start ollama", "set up an LLM", "configure harbor", "manage services"…
harbor-daytona
Use Harbor's Daytona sandbox platform for computer use — creating sandboxes, taking screenshots, sending mouse/keyboard input, and building agent loops. Use when the user wants to interact with a GUI, automate a desktop, do computer use, control a browser visually, or run Claude computer use against a Daytona sandbox.
boost-modules
Skill "boost-modules" from av/harbor, covering harbor boost custom modules, module structure, quick reference, output methods and stream text to client.
background-task
Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.
query-snmp-traps
Query SNMP trap logs through Netdata Cloud or directly from a Netdata Agent. Use when the user asks about SNMP traps, trap journal entries, trap severities, trap categories, trap senders, deduplication summaries, decode errors, TRAP fields, TRAPVAR indexed varbind fields, TRAPJSON varbind audit data, or how to inspect…