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 service-dependenciesgit 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/service-dependencies)<a href="https://agentmods.dev/skills/anatolykoptev/dozor/service-dependencies"><img src="https://agentmods.dev/badge/skills/anatolykoptev/dozor/service-dependencies/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/service-dependencies"><img src="https://agentmods.dev/badge/skills/anatolykoptev/dozor/service-dependencies.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.00041 | $0.00652 |
| Opus 5 | $0.00020 | $0.00326 |
| Sonnet 5 | $0.00008 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
service-dependencies 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 11d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service Dependencies
Know the dependency graph before restarting anything. Wrong order causes cascading failures.
Docker Compose Stack
Map your service dependencies. Example layout:
database (:5432)
vector-db (:6333)
redis (:6379)
message-queue (:5672)
↓
api-service (:8000) ← needs database, vector-db, redis, message-queue
↓
worker-service (:8080) ← needs api-service
mcp-service (:8001) ← needs database, vector-db
search-engine (:8888) ← standalone
llm-proxy ← standalone
Restart Order
When restarting multiple services, follow this order:
- Infrastructure (no deps): database, vector-db, redis, message-queue
- Standalone services: llm-proxy, search-engine
- API services (need infra up + healthy)
- Workers/consumers (need API services)
- MCP/gateway services (need data stores)
Wait 10-15s between tiers for services to become healthy.
Dependency Chain Example
Database issues cascade: database → api-service → worker-service
1. Check worker-service — if down, check api-service first
2. Check api-service — if down, check database first
3. Check database — if down, restart database, wait 10s
4. Restart api-service, wait 10s
5. Restart worker-service
6. Verify: server_inspect(mode: "health")
Never restart downstream services without checking their upstream dependencies.
Systemd Services (user-level)
search-service (:8890) ← may need search-engine
agent-service (:18790) ← may need llm-proxy
Use server_services(action: "restart", service: NAME) for these.
Remote Server (restart order)
1. database ← database first
2. redis ← cache
3. app-server ← app server (needs DB + cache)
4. web-server ← web server (needs app upstream)
Use server_remote(action: "restart", service: NAME) for these.
Full Stack Restart
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.
- 11d ago First seen · 94 lines · 41 tokens per session scan A ed815312e18d
service-dependencies is a skill published in the GitHub repository anatolykoptev/dozor (5 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 652 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
alembic-migration
Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.
后端编码
A backend coding guide covering web APIs, databases, error handling, logging, and endpoint tests. Backend code runs on servers and handles data and application operations.
odoo-multi-company
Disambiguate Odoo accounting records across multiple companies. Use whenever an agent reads or writes ledger records (account.move, account.account, account.journal, account.tax, account.payment) on an instance that may host several companies. Covers reading the [Company X] label suffix, filtering by companyid…
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…
disk-space-basic
Monitor system disk space and storage usage safely.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.