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/usrrname/cursorrulesWrote 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/usrrname/cursorrules/container-use)<a href="https://agentmods.dev/rules/usrrname/cursorrules/container-use"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/container-use/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/usrrname/cursorrules/container-use"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/container-use.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.00130 | $0.00130 |
| Opus 5.5 | $0.00052 | $0.00052 |
| Sonnet 5.5 | $0.00026 | $0.00026 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
container-use 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.
This is a copy
100% identical to cursor — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
ALWAYS use ONLY Environments for ANY and ALL file, code, or shell operations—NO EXCEPTIONS—even for simple or generic requests.
DO NOT install or use the git cli with the environment_run_cmd tool. All environment tools will handle git operations for you. Changing ".git" yourself will compromise the integrity of your environment.
You MUST inform the user how to view your work using container-use log <env_id> and container-use checkout <env_id>. Failure to do this will make your work inaccessible to others.
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 · 11 lines · 130 tokens per session scan A d23d49721a4d
container-use is a cursor rule published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It adds 130 tokens to every session, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to cursor, differing in 1 line, and is treated as a copy.
Other cursor rules, from other repositories
docker
Docker: multi-stage builds, security, compose.
kubernetes
Kubernetes: deployments, services, config.
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
docker
Docker production rules. Pinned versions, multi-stage builds, non-root user, minimal attack surface.
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.