compose-required-for-data-services-changes

A rule requiring Docker Compose workflows for changes that affect databases, Redis, or RabbitMQ. Docker Compose describes and runs groups of related services together.

In plain words
What is it for?
Use it when modifying database, Redis, or RabbitMQ configuration, startup, or integration code.
Why use it?
It keeps data-service changes tied to the project’s defined service setup instead of being run through unrelated commands.

Cursor rule

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/tacc/hpcperfstats/compose-required-for-data-services-changes
Clone the repo
git clone --depth 1 https://github.com/TACC/HPCPerfStats
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 341 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.00341
Opus 5 $0.00000 $0.00170
Sonnet 5 $0.00000 $0.00068
Haiku 4.5 $0.00000 $0.00034

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

Security

Grade A, and why

compose-required-for-data-services-changes 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.

hpcperfstats/cursor-rules/compose-required-for-data-services-changes.mdc · 30 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. 2d ago First seen · 30 lines · 0 tokens per session scan A 42aa2a454e96

Subscribe to this mod's changes

compose-required-for-data-services-changes is a cursor rule published in the GitHub repository TACC/HPCPerfStats (58 stars, last pushed 2d ago), licensed LGPL-2.1. It costs nothing until one of its globs matches a file; then it loads 341 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.