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/caipe-io/ai-platform-engineering/docker-compose-first-installgit clone --depth 1 https://github.com/caipe-io/ai-platform-engineeringWhat 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.00030 | $0.00203 |
| Opus 5 | $0.00015 | $0.00102 |
| Sonnet 5 | $0.00006 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
docker-compose-first-install 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.
What it actually says
Docker Compose First Install
When a task touches docker-compose.yaml, docker-compose.dev.yaml,
.env.example, release image tags, Compose profiles, Keycloak/OpenFGA/RAG
defaults, or first-launch UI behavior, follow:
.claude/skills/docker-compose-first-install/SKILL.md
The plain OSS path must work from:
cp .env.example .env
COMPOSE_PROFILES="mcp-servers,caipe-ui-prod,rbac,caipe-supervisor,dynamic-agents,rag,caipe-mongodb,web_ingestor" \
docker compose --env-file .env -f docker-compose.yaml up -d
Do not add Slack/Webex bots to the default all-in-one path. Do not add AI attribution comments.
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 · 24 lines · 30 tokens per session scan A d8267f5efeae
docker-compose-first-install is a cursor rule published in the GitHub repository caipe-io/ai-platform-engineering (403 stars, last pushed 4d ago), licensed Apache-2.0. It adds 30 tokens to every session and 203 once invoked, about $0.0002 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
kandev-pr-fixup
Kandev PR fixup workflow prompt for Cursor agents.
devops-infrastructure
DevOps and infrastructure: Docker, Kubernetes, Terraform, CI/CD. Load when editing Dockerfiles, compose, k8s manifests, Terraform, or workflow YAML — not for application code.
030-wave-execution
When executing session plan waves via /go command — task sequencing, quality checks, progress tracking.
conventional-commits
Always use Conventional Commits for git commit messages.
deployment
Rails Deployment with Kamal.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.