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-operator-patterns)<a href="https://agentmods.dev/rules/cockroachdb/cursor-plugin/cockroachdb-operator-patterns"><img src="https://agentmods.dev/badge/rules/cockroachdb/cursor-plugin/cockroachdb-operator-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-operator-patterns"><img src="https://agentmods.dev/badge/rules/cockroachdb/cursor-plugin/cockroachdb-operator-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.04346 |
| Opus 5.5 | $0.00000 | $0.01738 |
| Sonnet 5.5 | $0.00000 | $0.00869 |
| Haiku 4.5 | $0.00000 | $0.00435 |
Grade C, and why
cockroachdb-operator-patterns 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
2. Remove the store directory: `rm -rf <store-path>` How it starts
The opening of the file, as written. The whole thing — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CockroachDB Operator & SRE Patterns
Operational procedures from the CockroachDB Runbook Template, Query Parallelism, and cockroachdb-best-practices-demo.
1. Day-1 Operational Readiness
Before operating a CockroachDB cluster, verify this checklist:
| Check | Requirement |
|---|---|
| Clock sync | NTP configured on all nodes, --max-offset set (default 500ms) |
| Load balancer | HAProxy or cloud LB in front of all nodes |
| Connection pooling | Configured per app (4 x vCPUs pool size) |
| Replication factor | 3 for zone survival, 5 for region survival |
| Storage | Dedicated SSDs for CockroachDB store directory |
| One node per OS/container | Never run multiple cockroach processes on same host |
| DBA role | Custom role with appropriate grants (never use root in production) |
| TLS certificates | Generated and distributed; sslmode=verify-full enforced |
| Backup schedule | Automated via CREATE SCHEDULE FOR BACKUP |
| Monitoring | Metrics exported to Prometheus/Datadog/Grafana |
| Alerting | Alert rules configured per Section 4 thresholds |
Key terms:
- Node = one
cockroachserver process (NOT the VM/container) - Cluster = set of connected CockroachDB nodes forming one system
- Range = ~512MB chunk of data, the unit of replication and distribution
2. Pre-Check Before Any Maintenance
✅ ALWAYS: Run these before ANY maintenance operation
-- Verify all nodes are live and available
SELECT node_id, is_live, is_available FROM crdb_internal.gossip_nodes;
-- Check for running jobs that might conflict
SELECT job_id, job_type, description, status, fraction_completed
FROM crdb_internal.jobs WHERE status = 'running';
-- Verify range health
SELECT count(*) AS total_ranges,
count(*) FILTER (WHERE array_length(replicas, 1) < 3) AS under_replicated
FROM crdb_internal.ranges;
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 91d749a73f18
- 1mo ago First seen · 500 lines · 0 tokens per session scan C 566e39923aca
cockroachdb-operator-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 4,346 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-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.