dockerignore-test-artifacts-sync

A Docker build rule that keeps the list of files excluded from the build context aligned with test and development-only folders.

In plain words
What is it for?
Use it when maintaining .dockerignore files and deciding which test or development paths Docker should not receive.
Why use it?
It reduces unnecessary files sent to Docker and helps keep production image builds focused on application files.

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/dockerignore-test-artifacts-sync
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 1,310 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.01310
Opus 5 $0.00000 $0.00655
Sonnet 5 $0.00000 $0.00262
Haiku 4.5 $0.00000 $0.00131

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

Security

Grade C, and why

dockerignore-test-artifacts-sync 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 3d 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.

- **`.git/`** — intentional include for SPA commit bake (`Dockerfile` `frontend-builder` `COPY .git` + `git rev-parse`). **`hpcperfstats-base` must `rm -rf /home/hpcperfstats/.git` immediately after `COPY . .`** so the r
hpcperfstats/cursor-rules/dockerignore-test-artifacts-sync.mdc · 77 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. 3d ago First seen · 77 lines · 0 tokens per session scan C 3332cca382c1

Subscribe to this mod's changes

dockerignore-test-artifacts-sync is a cursor rule published in the GitHub repository TACC/HPCPerfStats (58 stars, last pushed 3d ago), licensed LGPL-2.1. It costs nothing until one of its globs matches a file; then it loads 1,310 tokens. 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-30.