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.
git clone --depth 1 https://github.com/dobryakov/cursor-rulesWrote 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/rules/dobryakov/cursor-rules/infrastructure-rules)<a href="https://agentmods.dev/rules/dobryakov/cursor-rules/infrastructure-rules"><img src="https://agentmods.dev/badge/rules/dobryakov/cursor-rules/infrastructure-rules/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/rules/dobryakov/cursor-rules/infrastructure-rules"><img src="https://agentmods.dev/badge/rules/dobryakov/cursor-rules/infrastructure-rules.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.00301 | $0.00301 |
| Opus 5.5 | $0.00120 | $0.00120 |
| Sonnet 5.5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
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 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.
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). 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 causesContainerConfigKeyError. Always usedocker composecommand (space, not hyphen). - Do not include
version:field indocker-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
crontabsyntax) for manual execution, and, if possible, automate them within a dedicatedschedulercontainer. - Making the project plan or tasks list, make sure you use database migrations.
- Do not add
Dockerfileto the.dockerignore. - If the
.envconfiguration was changed OR environment variables indocker-compose.ymlwas changed, rundocker compose up -d --force-recreate --no-depsinstead ofrestart.
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 · 18 lines · 301 tokens per session scan A ba7891a1db45
infrastructure-rules is a cursor rule published in the GitHub repository dobryakov/cursor-rules (2 stars, last pushed 4mo ago), licensed MIT. It adds 301 tokens to every session, about $0.0012 per session on Opus 5.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.
Other cursor rules, from other repositories
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
hack
Hack is local-first. This project uses hack for local runtime orchestration (compose + DNS/TLS + logs + sessions). Prefer hack when shell access is available. Use MCP only when shell access is unavailable.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
container-rightsizer
Rightsizes container CPU and memory requests and limits using real usage data. Reduces requested resources without hitting OOMKills or CPU throttling.