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 agentmods add rules/ivangrynenko/cursorrules/docker-compose-standardsgit clone --depth 1 https://github.com/ivangrynenko/cursorrulesWhat 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 | $0.00004 | $0.00650 |
| Opus 5 | $0.00002 | $0.00325 |
| Sonnet 5 | $0.00001 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
docker-compose-standards 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 2d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule Details
-
Name: docker_compose_best_practices
-
Description: Enforces best practices in docker-compose files to ensure maintainability, security, and consistency
Filters
- file name:
docker-compose\\.ya?ml$ - event:
(file_create|file_modify)
Rejections
- Conditions:
- pattern
^\\s*version\\s*:– The 'version' field is deprecated in Docker Compose files. Compose files are now version-less by default.
- pattern
Rejections
- Conditions:
- pattern
^( |\t)– Inconsistent indentation detected. Use 2 spaces for indentation.
- pattern
Rejections
- Conditions:
- pattern
^\\s*links\\s*:– The 'links' key is deprecated. Use networks and service names for inter-service communication.
- pattern
Rejections
- Conditions:
- pattern
^\\s*image\\s*:\\s*[^:]+$– Specify an explicit image tag to ensure consistency.
- pattern
Rejections
- Conditions:
- pattern
^\\s*privileged\\s*:\\s*true– Running services in privileged mode is discouraged for security reasons.
- pattern
Rejections
- Conditions:
- pattern
^\\s*services\\s*:\\s*[^\\n]+\\n(?!.*\\blimits\\b)– Define resource limits for each service to prevent resource exhaustion.
- pattern
Suggestions
- Guidance: To adhere to Docker Compose best practices:
-
Omit the 'version' field: Compose files are version-less by default.
services: web: image: nginx -
Use consistent indentation: Use 2 spaces for indentation.
services: web: image: nginx -
Avoid 'links' key: Use networks and service names for service communication.
services: web: image: nginx networks: - my-network db: image: mysql networks: - my-network networks: my-network: -
Specify explicit image tags: Prevent unintended updates by defining image tags.
services: web: image: nginx:1.21.0 -
Avoid privileged mode: Do not use 'privileged: true'. Grant specific capabilities if necessary.
services: web: image: nginx cap_add: - NET_ADMIN
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.
- 2d ago First seen · 107 lines · 4 tokens per session scan A 9f57fad3c69f
docker-compose-standards is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (87 stars, last pushed 10mo ago), licensed MIT. It adds 4 tokens to every session and 650 once invoked, about $0.0000 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-30.
Other cursor rules, from other repositories
angular
Angular: signals, standalone components, RxJS patterns.
django
Django: models, views, ORM best practices.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
rust
Rust patterns: ownership, Result types, iterators.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.