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/benwilcock/rhdh-lab/container-lifecyclegit clone --depth 1 https://github.com/benwilcock/rhdh-labWhat 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.00798 | $0.00798 |
| Opus 5 | $0.00399 | $0.00399 |
| Sonnet 5 | $0.00160 | $0.00160 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
container-lifecycle 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Container Lifecycle Management
ALWAYS Use the rhdh-lab CLI
The workspace provides a unified lab script that MUST be used for starting and stopping containers.
Starting Containers
./lab up # Start everything (customized + orchestrator), tail logs
./lab up --no-logs # Start everything, return to prompt
./lab up --baseline # Pristine RHDH (no customizations, no orchestrator)
Lightspeed AI chat is always included in RHDH 1.10+. Configure your LLM provider in rhdh-customizations/.env (e.g. ENABLE_VLLM=true for LM Studio).
Stopping Containers
./lab down # Stop all containers (keep volumes)
./lab down --volumes # Stop and remove all data (clean slate)
./lab down always removes customization copies from rhdh-local/ (restores pristine state).
Viewing Status and Logs
./lab status # Show running containers
./lab logs # Follow all container logs
./lab logs rhdh # Follow a specific service
Network Namespace Sharing (CRITICAL)
Several containers use network_mode: "service:rhdh", sharing RHDH's network namespace:
lightspeed-core(port 8080; Lightspeed Core + Llama Stack in one container)
Why this matters:
- When RHDH restarts, it gets a NEW network namespace
- Containers in
network_mode: "service:rhdh"stay in the OLD namespace - Result: 504 Gateway Timeout errors -- containers appear "running" but are unreachable
- Solution: ALWAYS restart ALL containers together using
./lab
FORBIDDEN Operations
# NEVER do this when orchestrator/lightspeed are enabled:
podman compose restart rhdh
podman compose restart lightspeed-core
podman compose down && podman compose up -d
podman compose -f compose.yaml -f orchestrator/compose.yaml restart
REQUIRED Operations
# ALWAYS do this instead:
./lab down
./lab up
Exception: If running ONLY base RHDH via --baseline (no lightspeed, no orchestrator), direct podman compose restart rhdh is acceptable for config-only changes.
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 · 99 lines · 798 tokens per session scan A 4c039660d6dc
container-lifecycle is a cursor rule published in the GitHub repository benwilcock/rhdh-lab (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 798 tokens to every session, about $0.0040 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-31.
Other cursor rules, from other repositories
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
backend
Backend development rules for TT Studio - AI model management backend.
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.
hack
Hack v3 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.
colima-docker-runtime
This workspace uses Colima for Docker; use compose-backed tests when Colima is running.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.