generated-file-patterns

A list of generated, temporary, and binary file patterns that should be left out of pull-request review. A pull request is a proposed set of code changes for review before merging.

In plain words
What is it for?
Use it to decide which files reviewers should skip, including dependency lockfiles, generated code, build directories, images, fonts, media, and binaries.
Why use it?
It keeps review focused on human-written source and configuration instead of lockfiles, build output, maps, images, archives, and compiled 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/andyzengmath/soliton/generated-file-patterns
Clone the repo
git clone --depth 1 https://github.com/andyzengmath/soliton
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 339 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00339
Opus 5 $0.00000 $0.00169
Sonnet 5 $0.00000 $0.00068
Haiku 4.5 $0.00000 $0.00034

Measured yesterday against content hash 0ae28a959165, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

generated-file-patterns 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 yesterday.

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.

rules/generated-file-patterns.mdc · 24 lines

What it actually says

Auto-Generated Files (skip review)

  • *.lock, package-lock.json, yarn.lock, pnpm-lock.yaml
  • Cargo.lock, Gemfile.lock, poetry.lock, go.sum, composer.lock
  • *.min.js, *.min.css, *.bundle.js, *.chunk.js, *.map
  • *.generated.*, *.auto.*, *_generated.*
  • *.pb.go, *.pb.ts, *_pb2.py
  • dist/, build/, out/, .next/, coverage/
  • node_modules/, vendor/, __pycache__/, *.pyc

Binary Files (always skip)

  • Images: *.png, *.jpg, *.jpeg, *.gif, *.ico, *.webp, *.bmp, *.tiff
  • Fonts: *.woff, *.woff2, *.ttf, *.eot, *.otf
  • Archives: *.pdf, *.zip, *.tar, *.gz, *.bz2, *.7z, *.rar
  • Binaries: *.wasm, *.so, *.dll, *.dylib, *.exe, *.bin, *.dat
  • Media: *.mp3, *.mp4, *.wav, *.avi
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. yesterday First seen · 24 lines · 0 tokens per session scan A 0ae28a959165

Subscribe to this mod's changes

generated-file-patterns is a cursor rule published in the GitHub repository andyzengmath/soliton (1 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 339 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-31.