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/abderrahimghazali/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/abderrahimghazali/cursor-rules/docker-compose-standards)<a href="https://agentmods.dev/rules/abderrahimghazali/cursor-rules/docker-compose-standards"><img src="https://agentmods.dev/badge/rules/abderrahimghazali/cursor-rules/docker-compose-standards/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/abderrahimghazali/cursor-rules/docker-compose-standards"><img src="https://agentmods.dev/badge/rules/abderrahimghazali/cursor-rules/docker-compose-standards.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.00004 | $0.00911 |
| Opus 5.5 | $0.00002 | $0.00364 |
| Sonnet 5.5 | $0.00001 | $0.00182 |
| Haiku 4.5 | $0.00000 | $0.00091 |
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 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.
What it actually says
1. **Omit the 'version' field**: Compose files are version-less by default.
```yaml
services:
web:
image: nginx
```
2. **Use consistent indentation**: Use 2 spaces for indentation.
```yaml
services:
web:
image: nginx
```
3. **Avoid 'links' key**: Use networks and service names for service communication.
```yaml
services:
web:
image: nginx
networks:
- my-network
db:
image: mysql
networks:
- my-network
networks:
my-network:
```
4. **Specify explicit image tags**: Prevent unintended updates by defining image tags.
```yaml
services:
web:
image: nginx:1.21.0
```
5. **Avoid privileged mode**: Do not use 'privileged: true'. Grant specific capabilities if necessary.
```yaml
services:
web:
image: nginx
cap_add:
- NET_ADMIN
```
6. **Define resource limits**: Prevent services from consuming excessive resources.
```yaml
services:
web:
image: nginx
deploy:
resources:
limits:
cpus: '0.50'
memory: '512M'
```
Implementing these practices ensures secure, maintainable, and consistent Docker Compose configurations.
examples:
- input: | version: '3' services: web: image: nginx links: - db privileged: true db: image: mysql output: | services: web: image: nginx:1.21.0 networks: - my-network deploy: resources: limits: cpus: '0.50' memory: '512M' db: image: mysql:5.7 networks: - my-network networks: my-network: metadata: priority: high version: 1.0
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 · 139 lines · 4 tokens per session scan A 1a014cdac506
docker-compose-standards is a cursor rule published in the GitHub repository abderrahimghazali/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 4 tokens to every session and 911 once invoked, about $0.0000 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 cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
cloud-native-and-kubernetes-expertise-rules
Cloud-native and Kubernetes rules guide technical documentation about Kubernetes, a system for running containerized applications. They cover versions, major cloud providers, security, troubleshooting, and performance settings.
containerization-rules
A collection of coding rules covering frontend, backend, AI, DevOps, and other areas, including Dockerfile practices. Dockerfiles describe how to build software containers.
containerization
Container and Docker best practices.