jpa

A set of rules for using Spring Data JPA, the Java framework for mapping application objects to database records. It covers entities, repositories, database transactions, query performance, and data-transfer objects.

In plain words
What is it for?
Use it when creating or changing JPA entities, repositories, queries, pagination, transactions, database writes, or read-only projections.
Why use it?
It helps avoid common database problems such as loading records one by one, keeping transactions open too long, exposing database entities directly, or using unsafe SQL.

Cursor rule for Cursor

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/goranerhartic/cursor-development-rules/jpa
Clone the repo
git clone --depth 1 https://github.com/GoranErhartic/cursor-development-rules

Made for: Cursor.

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 282 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.00014 $0.00282
Opus 5 $0.00007 $0.00141
Sonnet 5 $0.00003 $0.00056
Haiku 4.5 $0.00001 $0.00028

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

Security

Grade A, and why

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

.cursor/rules/languages/java/jpa.mdc · 31 lines

What it actually says

Spring Data JPA

Entities

  • @Entity, @Table; @Id, @GeneratedValue; @Column; @OneToMany, @ManyToOne with FetchType; avoid N+1 (use JOIN FETCH or entity graph).
  • Use records or DTOs for read-only projections (interface or class) to limit loaded data.

Repositories

  • Extend JpaRepository; derived queries (findByX); @Query for JPQL or native (use native with care, parameterized); @Modifying for update/delete with @Transactional.
  • Use Pageable for pagination; return Page or Slice.

Transactions

  • @Transactional on service methods; readOnly = true for read-only; propagation for nested; rollback on runtime exceptions by default.
  • Keep transactions short; do not hold across HTTP or long operations.

Conventions

  • Single aggregate per transaction when possible; avoid N+1; use projections for lists; version for optimistic locking; do not expose entities directly in API (map to DTOs).

Anti-Patterns

  • N+1 queries; long transactions; exposing entities in API; raw SQL with concatenation; missing @Transactional on write

See also: validation.mdc, error-handling.mdc, ../../patterns/architecture.mdc

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 · 31 lines · 14 tokens per session scan A 6546a6e07f4a

Subscribe to this mod's changes

jpa is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 282 once invoked, about $0.0001 per session on Opus 5. 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.