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 deploymentgit 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/deployment)<a href="https://agentmods.dev/skills/anatolykoptev/dozor/deployment"><img src="https://agentmods.dev/badge/skills/anatolykoptev/dozor/deployment/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/deployment"><img src="https://agentmods.dev/badge/skills/anatolykoptev/dozor/deployment.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.00040 | $0.00662 |
| Opus 5.5 | $0.00016 | $0.00265 |
| Sonnet 5.5 | $0.00008 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
deployment 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 1mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment
Safe deployment flow: pre-check, deploy, verify.
Deploy Flow
1. PRE-CHECK
- server_inspect(mode: "health") — are all services healthy?
- server_inspect(mode: "overview") — enough disk/memory for build?
- If issues exist: fix first, then deploy
2. DEPLOY
- server_deploy(project_path: PATH, build: true, pull: true)
- Returns deploy_id for status polling
3. MONITOR
- server_deploy(deploy_id: ID) — poll until complete
- Watch for build errors, timeout (5 min max)
4. VERIFY
- server_inspect(mode: "health") — all services came back?
- server_triage() — any new issues?
- If service is down after deploy: check logs immediately
5. NOTIFY
- Report success/failure to user
- If failed: include error details and what was rolled back
Pre-Deploy Checklist
| Check | Tool | Threshold |
|---|---|---|
| All services healthy | server_inspect(mode: "health") | No exited/unhealthy |
| Disk space | server_inspect(mode: "overview") | < 80% used |
| Memory available | server_inspect(mode: "overview") | > 1GB free |
| No active incidents | server_triage() | No P0 issues |
If any check fails, warn user before proceeding.
Docker Compose Deploy
Standard deployment for a Docker Compose project:
server_deploy(project_path: "/path/to/your/project")
Deploy specific services only:
server_deploy(project_path: "/path/to/your/project", services: ["api-service", "worker-service"])
Skip pull (local changes only):
server_deploy(project_path: "/path/to/your/project", pull: false)
Post-Deploy Issues
Service Won't Start After Deploy
- server_inspect(mode: "logs", service: NAME, lines: 50) to check startup errors
- Common causes: config mismatch, missing env vars, port conflict
- If code issue: escalate to devops
Performance Degradation After Deploy
- server_inspect(mode: "overview") to check resource usage
- Compare with pre-deploy baseline
- May need container resource limit adjustment
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.
- 1mo ago First seen · 89 lines · 40 tokens per session scan A c4f504064ee5
deployment is a skill published in the GitHub repository anatolykoptev/dozor (6 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 662 once invoked, about $0.0002 per session on Opus 5.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
04-security
A security and operations guide for deploying Dify, an open-source platform for building AI applications, in production.
cloudstudio_deploy
Deploy static sites to CloudStudio sandbox workspaces or take published sites offline. This skill should be used when users want to deploy a local build directory (e.g. dist/, build/, out/) to a CloudStudio workspace, preview or publish a static site with a shareable URL, or unpublish an existing deployment.
cloudflare-temporary-deploy
Deploy a Worker live, no account, via wrangler --temporary.
tensorrt-llm
High-throughput LLM inference on NVIDIA GPUs.
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
lambdasim
Run the studio's per-project NLP Lambda path locally with lambdasim, haven's AWS Lambda stand-in: functions, invokes and response streams answered on this stack's nlpgo. Use when someone says 'haven lambda', 'lambdasim', 'haven up +lambda', 'haven sim lambda', 'NLP Lambda locally', 'per-project Lambda'…