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-app-patterns)<a href="https://agentmods.dev/rules/cockroachdb/cursor-plugin/cockroachdb-app-patterns"><img src="https://agentmods.dev/badge/rules/cockroachdb/cursor-plugin/cockroachdb-app-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-app-patterns"><img src="https://agentmods.dev/badge/rules/cockroachdb/cursor-plugin/cockroachdb-app-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.06353 |
| Opus 5.5 | $0.00000 | $0.02541 |
| Sonnet 5.5 | $0.00000 | $0.01271 |
| Haiku 4.5 | $0.00000 | $0.00635 |
Grade A, and why
cockroachdb-app-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 7d 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 — 714 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CockroachDB Application Patterns
These rules encode production-tested patterns from cockroachdb-best-practices-demo and cockroachdb-jdbc-wrapper. Follow them strictly when generating code that interacts with CockroachDB.
1. Transaction Retry Logic (MANDATORY)
CockroachDB defaults to SERIALIZABLE isolation — the strongest level. This means any two concurrent transactions touching the same rows may produce a SQLSTATE 40001 (serialization failure). Applications MUST implement retry logic.
Retryable Error Codes
| SQLSTATE | Meaning | Action |
|---|---|---|
40001 |
Serialization failure (transaction conflict) | ALWAYS retry the entire transaction |
08001 |
Unable to establish connection | Retry with backoff |
08003 |
Connection does not exist | Retry with new connection |
08004 |
Connection rejected by server | Retry with backoff |
08006 |
Connection failure during transaction | Retry with new connection |
08007 |
Transaction resolution unknown | Retry with new connection |
08S01 |
Communication link failure | Retry with new connection |
57P01 |
Admin shutdown (node drain/restart) | Retry with backoff |
Retry Strategy
- Use exponential backoff with jitter (not fixed delays)
- Recommended: base 200ms, multiplier 2×, jitter factor 0.5
- Max attempts: 3–5 for interactive, 5–10 for background/batch
- Retry the ENTIRE transaction — not just the failed statement
⛔ ANTI-PATTERN: Savepoint-Based Retry
// ❌ WRONG — This does NOT work with CockroachDB
conn.setAutoCommit(false);
Savepoint sp = conn.setSavepoint("cockroach_restart");
try {
// ... SQL operations ...
conn.commit();
} catch (SQLException e) {
if ("40001".equals(e.getSQLState())) {
conn.rollback(sp); // ❌ CockroachDB aborts the ENTIRE txn on 40001
// retrying here is USELESS — the transaction is dead
}
}
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.
- 7d ago Changed b40adb72a1e3
- 1mo ago First seen · 714 lines · 0 tokens per session scan A 2358f773451f
cockroachdb-app-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 6,353 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.