container-naming

A naming rule for a Docker Compose development setup. Docker Compose runs related application containers together.

In plain words
What is it for?
Use it when identifying or referring to the Compose stack and its containers; the stack is named laborforge-dev.
Why use it?
It keeps the setup and its individual containers named predictably.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/ericlortie/laborforge-release/container-naming
Clone the repo
git clone --depth 1 https://github.com/EricLortie/laborforge-release

Made for: Cursor.

Per session 1,845 This file is loaded in full into every session.
When invoked 1,845 The same file — it is already loaded in full.
Security scan C 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01845 $0.01845
Opus 5 $0.00923 $0.00923
Sonnet 5 $0.00369 $0.00369
Haiku 4.5 $0.00185 $0.00185

Measured 2d ago against content hash 50802a44027c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

container-naming scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

2. Clear Python cache: `find . -type d -name __pycache__ -exec rm -rf {} +`
.cursor/rules/container-naming.mdc · 228 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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.

  1. 2d ago First seen · 228 lines · 1,845 tokens per session scan C 50802a44027c

Subscribe to this mod's changes

container-naming is a cursor rule published in the GitHub repository EricLortie/laborforge-release (5 stars, last pushed 1mo ago), with no licence file. It adds 1,845 tokens to every session, about $0.0092 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.