managing-cluster-capacity

managing-cluster-capacity is a skill for Claude Code from cockroachdb/claude-plugin. It costs 95 tokens per session (3,420 once invoked), scanned A, a copy of managing-cluster-capacity, Apache-2.0.

A procedure for changing how much computing capacity a CockroachDB database cluster has. CockroachDB is a distributed SQL database, and its capacity settings differ between self-hosted and cloud deployments.

In plain words
What is it for?
It is for adding or removing nodes, changing node sizes or counts, adjusting provisioned virtual CPUs, controlling serverless costs, replacing hardware, and handling failed nodes.
Why use it?
It helps add, remove, or resize database resources while accounting for the deployment type and storage pressure.

Skill for Claude Code ✓ vendor

Written for Claude Code: shipped in a Claude Code plugin.

Part of the cockroachdb plugin — 34 skills, 3 agents, 2 hooks, 2 MCP servers shipped together

Good fit It is for adding or removing nodes, changing node sizes or counts, adjusting provisioned virtual CPUs, controlling serverless costs, replacing hardware, and handling failed nodes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cockroachdb/claude-plugin/managing-cluster-capacity
About the project

CockroachDB Plugin for Claude Code connects Claude Code to CockroachDB clusters, which are distributed databases, so the agent can work with schemas, SQL queries, and database operations. It is intended for developers, database administrators, and operators working with self-hosted or CockroachDB Cloud deployments. The catalogue entries provide its MCP connections, specialized agents, skills, and safety hooks.

cockroachdb/claude-plugin · 4 stars · on GitHub

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.

Any agent
npx skills add cockroachdb/claude-plugin --skill managing-cluster-capacity
Clone the repo
git clone --depth 1 https://github.com/cockroachdb/claude-plugin

Made for: Claude Code.

Or install cockroachdb, the plugin that ships this one along with the rest of its 34 skills, 3 agents, 2 hooks, 2 MCP servers.

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

agentmods badge for managing-cluster-capacity

README.md
[![agentmods](https://agentmods.dev/badge/skills/cockroachdb/claude-plugin/managing-cluster-capacity/github.svg)](https://agentmods.dev/skills/cockroachdb/claude-plugin/managing-cluster-capacity)
Your own site
<a href="https://agentmods.dev/skills/cockroachdb/claude-plugin/managing-cluster-capacity"><img src="https://agentmods.dev/badge/skills/cockroachdb/claude-plugin/managing-cluster-capacity/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.

agentmods 80×15 button for managing-cluster-capacity

Your own site · 80×15
<a href="https://agentmods.dev/skills/cockroachdb/claude-plugin/managing-cluster-capacity"><img src="https://agentmods.dev/badge/skills/cockroachdb/claude-plugin/managing-cluster-capacity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,420 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.1 $0.00095 $0.03420
Opus 5.5 $0.00038 $0.01368
Sonnet 5.5 $0.00019 $0.00684
Haiku 4.5 $0.00010 $0.00342

Measured 2mo ago against content hash fa02cbde2b83, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

managing-cluster-capacity scanned grade A 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 2mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -ks https://<node>:8080/_status/vars | grep '^capacity'
Origin

This is a copy

100% identical to managing-cluster-capacity — 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.

skills/cockroachdb-operations-and-lifecycle/managing-cluster-capacity/SKILL.md · 369 lines

How it starts

The opening of the file, as written. The whole thing — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Managing Cluster Capacity

Manages cluster capacity across all CockroachDB deployment tiers. What "capacity" means varies by tier — Self-Hosted manages individual nodes, Advanced/BYOC manage node count and machine size, Standard manages provisioned vCPUs, and Basic auto-scales with cost controls.

When to Use This Skill

  • Permanently removing a node from a cluster (Self-Hosted)
  • Adding nodes to increase capacity (Self-Hosted)
  • Scaling cluster node count or machine size (Advanced, BYOC)
  • Adjusting provisioned compute (Standard)
  • Managing costs on a serverless cluster (Basic)
  • Replacing hardware or migrating infrastructure (Self-Hosted, BYOC)
  • Replacing a failed or dead node (Self-Hosted)
  • Managing storage utilization and disk pressure (Self-Hosted)

For temporary maintenance (not capacity changes): Use performing-cluster-maintenance. For pre-operation health check: Use reviewing-cluster-health.


Step 1: Gather Context

Required Context

Question Options Why It Matters
Deployment tier? Self-Hosted, Advanced, BYOC, Standard, Basic Different capacity model per tier
Direction? Scale up (add capacity), Scale down (reduce capacity) Determines procedure

Additional Context (by tier)

If Self-Hosted (scaling down):

Question Options Why It Matters
How many nodes to remove? 1, multiple Multi-node decommission should be done simultaneously
Target node IDs? Node IDs from cockroach node status Required for CLI commands
Is the node alive or dead? Alive, Dead Dead nodes use a different procedure
Deployment platform? Bare metal, VMs, Kubernetes Changes CLI and cleanup steps
Current replication factor? 3, 5, custom Must have enough nodes remaining
Current node count? Number Validates remaining capacity
Storage utilization? Low (<60%), Medium (60-80%), High (>80%) Determines urgency and whether storage maintenance is needed

Read the full file on GitHub · 369 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2mo ago First seen · 369 lines · 95 tokens per session scan A fa02cbde2b83

Subscribe to this mod's changes

managing-cluster-capacity is a skill published in the GitHub repository cockroachdb/claude-plugin (4 stars, last pushed 28d ago), licensed Apache-2.0. It adds 95 tokens to every session and 3,420 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to managing-cluster-capacity, differing in 0 lines, and is treated as a copy.

Related

managing-cluster-capacity compared with skills from other repositories

managing-cluster-capacity next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
managing-cluster-capacitycockroachdb/claude-pluginSkill428d agoApache-2.0A95Claude Code
managing-cluster-capacitycockroachdb/cursor-pluginSkill228d agoApache-2.0A95Cursor
provisioning-cluster-for-productioncockroachdb/cursor-pluginSkill228d agoApache-2.0A96Cursor
configuring-private-connectivitycockroachdb/cursor-pluginSkill228d agoApache-2.0A71Cursor
upgrading-cluster-versioncockroachdb/cursor-pluginSkill228d agoApache-2.0B79Cursor
designing-application-transactionscockroachdb/cursor-pluginSkill228d agoApache-2.0A102Cursor
auditing-table-statisticscockroachdb/cursor-pluginSkill228d agoApache-2.0A55Cursor