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.
npx agentmods add skills/cockroachdb/cursor-plugin/designing-multi-region-applicationsnpx skills add cockroachdb/cursor-plugin --skill designing-multi-region-applicationsgit 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/skills/cockroachdb/cursor-plugin/designing-multi-region-applications)<a href="https://agentmods.dev/skills/cockroachdb/cursor-plugin/designing-multi-region-applications"><img src="https://agentmods.dev/badge/skills/cockroachdb/cursor-plugin/designing-multi-region-applications.svg" alt="Measured on agentmods" 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 | $0.00089 | $0.03391 |
| Opus 5 | $0.00044 | $0.01695 |
| Sonnet 5 | $0.00018 | $0.00678 |
| Haiku 4.5 | $0.00009 | $0.00339 |
Grade A, and why
designing-multi-region-applications 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 5d 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.
This is a copy
100% identical to designing-multi-region-applications — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designing Multi-Region Applications
Guides developers through selecting the right multi-region pattern for their CockroachDB application and implementing it with proper validation. Covers the decision model for choosing between regular regional tables, REGIONAL BY ROW, GLOBAL tables, and manual geo-partitioning, plus a hands-on demo framework for comparing approaches.
Complement to other skills: For transaction design patterns, see designing-application-transactions. For SQL syntax and schema design, see cockroachdb-sql.
When to Use This Skill
- Deciding how to model multi-region read/write behavior in CockroachDB
- Choosing between active-active and active-passive architectures
- Evaluating
REGIONAL BY ROWvs manual geo-partitioning - Understanding
GLOBALtable behavior and trade-offs - Designing for local reads and writes in multiple regions
- Building or presenting a multi-region demo or workshop
- Validating leaseholder placement and zone configurations
- Optimizing cross-region transaction latency
Do not use this skill when the question is only about SQL syntax, indexing, or generic schema design with no multi-region decision involved.
Prerequisites
- Understanding of CockroachDB range architecture and leaseholder concepts
- A multi-region cluster with nodes started using
--locality=region=...,zone=...matching the regions used in the examples below. Without matching localities the DDL errors withregion "..." does not existand constraints like+region=...match no nodes. Quickest path locally:
For long-running clusters, see setting-up-local-cluster and add# 9-node demo with three regions, three AZs each — note --no-example-database cockroach demo --no-example-database --nodes=9 \ --demo-locality=region=NA-NE,az=1:region=NA-NE,az=2:region=NA-NE,az=3:region=NA-MW,az=1:region=NA-MW,az=2:region=NA-MW,az=3:region=EU-DE,az=1:region=EU-DE,az=2:region=EU-DE,az=3--locality=region=...,zone=...to eachcockroach startinvocation. - Knowledge of application write patterns (single-region vs multi-region)
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.
- 5d ago First seen · 335 lines · 89 tokens per session scan A 9f6ef7d95cfd
designing-multi-region-applications is a skill published in the GitHub repository cockroachdb/cursor-plugin (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 89 tokens to every session and 3,391 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to designing-multi-region-applications, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
designing-application-transactions
Guides application developers in designing correct and performant transaction patterns for CockroachDB, covering transaction lifetime, implicit vs explicit transactions, retry handling with exponential backoff, pushing invariants into SQL, selective pessimistic locking, set-based operations, connection pooling…
auditing-cloud-cluster-security
Audits the security posture of a CockroachDB cluster (Cloud or self-hosted) across network, authentication, authorization, encryption, audit logging, and backup dimensions. Use when assessing cluster security readiness, preparing for compliance reviews, or investigating security configuration gaps.
configuring-sso-and-scim
Configures SSO authentication and SCIM 2.0 provisioning for CockroachDB across four distinct layers — Cloud Console SSO (SAML/OIDC), DB Console SSO (OIDC), SQL/Cluster SSO (JWT or LDAP/AD), and SCIM 2.0 automated provisioning. Use when enabling centralized identity management, setting up SSO for compliance, or…
auditing-table-statistics
Audits optimizer table statistics for staleness, missing coverage, and data quality issues using SHOW STATISTICS. Use when diagnosing poor query performance, unexpected plan changes, or after bulk data changes to identify stale statistics requiring refresh via CREATE STATISTICS.
monitoring-background-jobs
Monitors CockroachDB background job health by identifying failed, paused, and long-running jobs using SHOW JOBS and SHOW AUTOMATIC JOBS. Surfaces schema changes, backups/restores, automatic statistics collection, and SQL stats compaction jobs without DB Console access. Use when investigating schema change delays…
profiling-statement-fingerprints
Ranks and analyzes statement fingerprints using aggregated SQL statistics from crdbinternal.statementstatistics to identify slow, resource-intensive, or error-prone query patterns. Use when investigating historical performance trends, identifying optimization opportunities, or diagnosing recurring slowness without DB…