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/lagoon-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.00000 | $0.00765 |
| Opus 5 | $0.00000 | $0.00382 |
| Sonnet 5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
lagoon-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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- lagoon-docker-compose-standards — 100% identical, 0 lines differ
What it actually says
Lagoon Docker Compose Standards
Ensures proper Docker Compose configuration for Lagoon deployments, following best practices and Lagoon-specific requirements.
actions:
-
type: enforce conditions:
-
pattern: "services:\s+\w+:\s+(?!.*labels:[\s\S]*lagoon)" message: "Add Lagoon labels to service definitions for proper Lagoon integration"
-
pattern: "version:\s*['"]*2" message: "Use Docker Compose format version 3 or higher for compatibility with modern Docker features"
-
pattern: "volumes:\s+[^:]+:\s+(?!.*delegated)" message: "Use 'delegated' mount consistency for better performance on macOS development environments"
-
pattern: "services:\s+\w+:\s+(?!.*restart:)" message: "Define restart policy for services to ensure proper behavior during deployment"
-
-
type: suggest message: |
Lagoon Docker Compose Best Practices:
Service Configuration
- Define service types via labels (e.g.,
lagoon.type: nginx) - Use proper image naming conventions (e.g.,
amazeeio/nginx-drupal:latest) - Set appropriate environment variables using Lagoon variables
- Define health checks for critical services
- Configure proper networking with Lagoon defaults
- Set resource constraints appropriate for each environment
Volume Configuration
- Use named volumes for persistent data
- Configure appropriate volume mounts with correct permissions
- Use 'delegated' mount consistency for macOS performance
- Avoid mounting the entire codebase when possible
Build Configuration
- Use build arguments appropriately
- Define proper Dockerfile paths
- Use multi-stage builds for smaller images
Example Service Configuration:
services: nginx: build: context: . dockerfile: nginx.dockerfile labels: lagoon.type: nginx lagoon.persistent: /app/web/sites/default/files/ volumes: - app:/app:delegated depends_on: - php environment: LAGOON_ROUTE: ${LAGOON_ROUTE:-http://project.docker.amazee.io} - Define service types via labels (e.g.,
-
type: validate conditions:
-
pattern: "services:\s+cli:\s+(?!.*build:)" message: "CLI service should have proper build configuration for Lagoon compatibility"
-
pattern: "services:\s+\w+:\s+(?!.*depends_on:)" message: "Define service dependencies for proper startup order and container relationships"
-
pattern: "networks:\s+(?!.*default:)" message: "Configure proper network settings for Lagoon compatibility and service communication"
-
pattern: "services:\s+mariadb:\s+(?!.*image:\s+amazeeio\/mariadb)" message: "Use Lagoon-provided MariaDB image for compatibility with Lagoon environment"
-
pattern: "services:\s+\w+:\s+environment:\s+(?!.*\$\{LAGOON)" message: "Use Lagoon environment variables with fallbacks for local development"
-
metadata: priority: high version: 1.1
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.
- 3d ago First seen · 92 lines · 0 tokens per session scan A cfa812b1fafc
lagoon-docker-compose-standards is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 765 tokens. 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
ankra-cli
Ankra CLI rules and best practices for managing Kubernetes clusters via the Ankra platform.
elixir-phoenix-docker-setup-cursorrules-prompt-fil
Cursor rules for Elixir development with Phoenix and Docker integration.
docker
Docker production rules. Pinned versions, multi-stage builds, non-root user, minimal attack surface.
yaml-config
Rules for YAML / config / infra files (Docker, K8s, Terraform, GitHub Actions, etc.).
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
deploy-arch-maintenance
部署架构文档维护规则(RULE-21/22/23/24/25)。当任务涉及部署、服务器、容器、端口、域名、CI/CD、新项目上线、技术架构设计、数据库操作时自动激活。.