CockroachDB Plugin for Cursor connects the Cursor coding agent to CockroachDB clusters for database work such as exploring schemas, writing SQL, debugging queries, and managing distributed clusters. It supports self-hosted and CockroachDB Cloud connections, and its catalogue add-ons provide database-focused agents, skills, rules, and instructions.
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.
git clone --depth 1 https://github.com/cockroachdb/cursor-pluginWrote 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.
[](https://agentmods.dev/rules/cockroachdb/cursor-plugin/cockroachdb-developer-patterns)<a href="https://agentmods.dev/rules/cockroachdb/cursor-plugin/cockroachdb-developer-patterns"><img src="https://agentmods.dev/badge/rules/cockroachdb/cursor-plugin/cockroachdb-developer-patterns/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.
<a href="https://agentmods.dev/rules/cockroachdb/cursor-plugin/cockroachdb-developer-patterns"><img src="https://agentmods.dev/badge/rules/cockroachdb/cursor-plugin/cockroachdb-developer-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.03955 |
| Opus 5.5 | $0.00000 | $0.01582 |
| Sonnet 5.5 | $0.00000 | $0.00791 |
| Haiku 4.5 | $0.00000 | $0.00396 |
Grade A, and why
cockroachdb-developer-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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CockroachDB Developer Patterns — JPA, Spring, JavaEE & Set-Based SQL
Framework-specific patterns from JPA Best Practices for CockroachDB, Transaction Retries Series, Set-Based Operations, and cockroachdb-best-practices-demo.
1. JPA/Hibernate Identity Generators
❌ NEVER: Use GenerationType.IDENTITY with CockroachDB
// BAD: IDENTITY disables Hibernate JDBC batching entirely.
// Hibernate must execute each INSERT individually to retrieve the generated ID.
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
✅ ALWAYS: Use UUID with GenerationType.AUTO
// GOOD: UUIDv4 generated in JVM — no DB round-trip, batching works, writes distributed
@Id
@GeneratedValue(strategy = GenerationType.AUTO)
@Column(columnDefinition = "UUID")
private UUID id;
✅ Alternative: Explicit UUID generator for clarity
@Id
@GeneratedValue
@GenericGenerator(name = "uuid", strategy = "org.hibernate.id.UUIDGenerator")
@Column(columnDefinition = "UUID")
private UUID id;
If numeric PKs are unavoidable:
// Use unordered_unique_rowid() from CockroachDB — randomly distributed, not sequential
// Or use a custom generator that batches Hi-Lo allocation from a sequence in the JVM
@Id
@GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "order_seq")
@SequenceGenerator(name = "order_seq", allocationSize = 50) // batch 50 IDs
private Long id;
// WARNING: Still creates some hot-spotting. UUID is strongly preferred.
2. Spring Boot Transaction Retry with AOP
The standard @Transactional annotation does NOT retry on 40001. Add an AOP aspect to intercept and retry.
✅ CORRECT: Spring AOP retry interceptor
@Aspect
@Order(Ordered.HIGHEST_PRECEDENCE) // Must run BEFORE @Transactional proxy
@Component
public class CockroachRetryAspect {
private static final int MAX_RETRIES = 5;
@Around("@annotation(transactional)")
public Object retryOnSerializationFailure(
ProceedingJoinPoint pjp, Transactional transactional) throws Throwable {
for (int attempt = 1; attempt <= MAX_RETRIES; attempt++) {
try {
return pjp.proceed();
} catch (TransientDataAccessException ex) {
Throwable root = ex.getMostSpecificCause();
if (root instanceof SQLException sql
&& "40001".equals(sql.getSQLState())
&& attempt < MAX_RETRIES) {
long backoff = Math.min(
(long)(Math.pow(2, attempt) * 200 + Math.random() * 1000), 15000);
Thread.sleep(backoff);
continue;
}
throw ex;
}
}
throw new ConcurrencyFailureException("Max retries exceeded for CockroachDB txn");
}
}
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.
- 8d ago Changed e9a59ed0f68c
- 1mo ago First seen · 474 lines · 0 tokens per session scan A 83342170fc74
cockroachdb-developer-patterns is a cursor rule published in the GitHub repository cockroachdb/cursor-plugin (2 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,955 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.
Other cursor rules, from other repositories
python-app
Here's how the python application is organized.
supabase-auth-security
Supabase auth security — enforces getUser() over getSession() on the server.
supabase-rls
Supabase Row Level Security enforcement.
schema-design
Database schema design conventions and standards. Apply when designing schema or migrations.
full-stack-ship-discipline
Require frontend changes and their DB/RPC/RLS/storage/secret dependencies to ship and be remotely verified together. Apply when implementing code that reads or writes backend state. Do not apply to plan- or present-then-stop audits; production data mutation still requires confirmation.
migration
A set of rules for writing database migration scripts, which are files that change a database's structure over time. It covers MySQL 8 tables, columns, filenames, locations, and required fields.