docker-compose-settings-example-sync

docker-compose-settings-example-sync is a cursor rule for Cursor from TACC/HPCPerfStats. It costs 0 tokens per session (980 once invoked), scanned A, original, LGPL-2.1.

A project rule for keeping docker-compose.settings.yaml.example synchronized with the real Docker Compose settings file. Docker Compose defines and runs multiple containers together.

In plain words
What is it for?
Use it when changing Docker Compose settings or bind mounts so the example file is updated at the same time.
Why use it?
It prevents the example configuration from becoming outdated when settings or mounted folders change.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it when changing Docker Compose settings or bind mounts so the example file is updated at the same time.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/tacc/hpcperfstats/docker-compose-settings-example-sync
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.

Clone the repo
git clone --depth 1 https://github.com/TACC/HPCPerfStats

Made for: Cursor.

Wrote 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.

agentmods badge for docker-compose-settings-example-sync

README.md
[![agentmods](https://agentmods.dev/badge/rules/tacc/hpcperfstats/docker-compose-settings-example-sync/github.svg)](https://agentmods.dev/rules/tacc/hpcperfstats/docker-compose-settings-example-sync)
Your own site
<a href="https://agentmods.dev/rules/tacc/hpcperfstats/docker-compose-settings-example-sync"><img src="https://agentmods.dev/badge/rules/tacc/hpcperfstats/docker-compose-settings-example-sync/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.

agentmods 80×15 button for docker-compose-settings-example-sync

Your own site · 80×15
<a href="https://agentmods.dev/rules/tacc/hpcperfstats/docker-compose-settings-example-sync"><img src="https://agentmods.dev/badge/rules/tacc/hpcperfstats/docker-compose-settings-example-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 980 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00980
Opus 5.5 $0.00000 $0.00392
Sonnet 5.5 $0.00000 $0.00196
Haiku 4.5 $0.00000 $0.00098

Measured 10d ago against content hash 5dbc9d6e7a8b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

docker-compose-settings-example-sync 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 10d 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.

hpcperfstats/cursor-rules/docker-compose-settings-example-sync.mdc · 56 lines

The source is not reproduced here

Licensed LGPL-2.1

The repository is licensed LGPL-2.1, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

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. 10d ago Changed 5dbc9d6e7a8b
  2. 1mo ago Changed · +1 lines 05ec9d90960a
  3. 1mo ago Changed 5eb8c6dcea0f
  4. 1mo ago First seen · 55 lines · 0 tokens per session scan A 2ebdb48eca8b

Subscribe to this mod's changes

docker-compose-settings-example-sync is a cursor rule published in the GitHub repository TACC/HPCPerfStats (59 stars, last pushed today), licensed LGPL-2.1. It costs nothing until one of its globs matches a file; then it loads 980 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.