infrastructure-rules

A set of infrastructure rules for running services on remote servers with Docker Compose. Docker packages an application with its dependencies, while Compose coordinates multiple containers.

In plain words
What is it for?
It guides container setup, service deployment, rebuild decisions, scheduled jobs, database migrations, environment changes, and Docker Compose commands.
Why use it?
It prevents deployment mistakes caused by outdated commands, incorrect container handling, or missing migration and configuration practices.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/dobryakov/cursor-rules/infrastructure-rules
Clone the repo
git clone --depth 1 https://github.com/dobryakov/cursor-rules
Per session 301 This file is loaded in full into every session.
When invoked 301 The same file — it is already loaded in full.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00301 $0.00301
Opus 5 $0.00151 $0.00151
Sonnet 5 $0.00060 $0.00060
Haiku 4.5 $0.00030 $0.00030

Measured yesterday against content hash ba7891a1db45, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

infrastructure-rules scanned grade A with 1 finding 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 yesterday.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

* Whenever possible, run commands inside containers — do not execute them on the host (exceptions: `docker`, `compose`, `curl`, `sh`, ask for additions).
en/rules/infrastructure-rules.mdc · 18 lines

What it actually says

Infrastructure and Containers

  • Work only on a remote server.
  • Deploy services in Docker and manage them via docker-compose.yml.
  • MUST use Docker Compose V2 (docker compose) instead of V1 (docker-compose). V1 is incompatible with newer Docker versions and causes ContainerConfig KeyError. Always use docker compose command (space, not hyphen).
  • Do not include version: field in docker-compose.yml — Docker Compose V2 does not require it and will show a warning if present.
  • Whenever possible, run commands inside containers — do not execute them on the host (exceptions: docker, compose, curl, sh, ask for additions).
  • When possible, reuse base images across different containers.
  • After making changes, evaluate whether a container rebuild (build) is required instead of just a restart (run).
  • If the project includes periodic tasks (cron jobs), document them (with ready-to-use crontab syntax) for manual execution, and, if possible, automate them within a dedicated scheduler container.
  • Making the project plan or tasks list, make sure you use database migrations.
  • Do not add Dockerfile to the .dockerignore.
  • If the .env configuration was changed OR environment variables in docker-compose.yml was changed, run docker compose up -d --force-recreate --no-deps instead of restart.
Changes

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.

  1. yesterday First seen · 18 lines · 301 tokens per session scan A ba7891a1db45

Subscribe to this mod's changes

infrastructure-rules is a cursor rule published in the GitHub repository dobryakov/cursor-rules (2 stars, last pushed 2mo ago), licensed MIT. It adds 301 tokens to every session, about $0.0015 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.