performing-cluster-maintenance

performing-cluster-maintenance is a skill for Claude Code from cockroachdb/claude-plugin. It costs 87 tokens per session (3,314 once invoked), scanned B, a copy of performing-cluster-maintenance, Apache-2.0.

A guide for carrying out planned maintenance on a CockroachDB database cluster, a group of database servers working together. The process depends on whether the cluster is self-managed or managed by CockroachDB.

In plain words
What is it for?
Use it to drain and restart self-hosted nodes, configure maintenance windows and patch deferrals, monitor managed maintenance, run validation checks, and prepare applications for maintenance events.
Why use it?
It clarifies what the operator must do before, during, and after maintenance, including when the service handles the work automatically. This reduces the risk of disrupting applications during patches, hardware changes, or configuration updates.

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 Use it to drain and restart self-hosted nodes, configure maintenance windows and patch deferrals, monitor managed maintenance, run validation checks, and prepare applications for maintenance events.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cockroachdb/claude-plugin/performing-cluster-maintenance
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 performing-cluster-maintenance
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 performing-cluster-maintenance

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/cockroachdb/claude-plugin/performing-cluster-maintenance"><img src="https://agentmods.dev/badge/skills/cockroachdb/claude-plugin/performing-cluster-maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,314 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. 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.00087 $0.03314
Opus 5.5 $0.00035 $0.01326
Sonnet 5.5 $0.00017 $0.00663
Haiku 4.5 $0.00009 $0.00331

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

Security

Grade B, and why

performing-cluster-maintenance scanned grade B with 2 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 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo systemctl stop cockroachdb

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 -E '^capacity( |_used|_available)'
Origin

This is a copy

100% identical to performing-cluster-maintenance — 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/performing-cluster-maintenance/SKILL.md · 380 lines

How it starts

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

Performing Cluster Maintenance

Manages planned cluster maintenance across all deployment tiers. For Self-Hosted, this means draining and restarting individual nodes. For Advanced/BYOC, this means configuring and managing maintenance windows for CRL-applied patches. For Standard and Basic, maintenance is fully managed with no customer action required.

When to Use This Skill

  • Planning OS patching, hardware changes, or configuration updates (Self-Hosted)
  • Configuring or modifying a maintenance window (Advanced, BYOC)
  • Setting patch deferral policies (Advanced, BYOC)
  • Monitoring during a CRL-managed maintenance event (Advanced, BYOC)
  • Running pre-maintenance validation checks (Self-Hosted, Advanced, BYOC)
  • Understanding how maintenance affects your application (all tiers)
  • Preparing applications for maintenance events (all tiers)

For permanent node removal: Use managing-cluster-capacity. For pre-maintenance health check: Use reviewing-cluster-health. For version upgrades: Use upgrading-cluster-version.


Step 1: Gather Context

Required Context

Question Options Why It Matters
Deployment tier? Self-Hosted, Advanced, BYOC, Standard, Basic Determines maintenance procedure
Goal? Plan maintenance, Configure maintenance window, Defer a patch, Monitor during maintenance, Prepare application Routes to the right procedure

Additional Context (by tier)

If Self-Hosted:

Question Options Why It Matters
Maintenance type? OS patching, Hardware change, Binary upgrade, Config change, Planned restart Affects sequencing and post-maintenance steps
Deployment platform? Bare metal, VMs, Kubernetes (Operator/Helm/manual) Changes drain and restart commands
Process manager? systemd, manual, container orchestrator Changes stop/start commands
Target node ID? Node ID Required for drain command
Long-running queries expected? Yes (increase drain timeout), No (default timeout) Determines drain-wait parameter

Read the full file on GitHub · 380 lines

Files

What ships with it

3 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 · 380 lines · 87 tokens per session scan B 172aab0d9cbd

Subscribe to this mod's changes

performing-cluster-maintenance is a skill published in the GitHub repository cockroachdb/claude-plugin (4 stars, last pushed 28d ago), licensed Apache-2.0. It adds 87 tokens to every session and 3,314 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). It is 100% identical to performing-cluster-maintenance, differing in 0 lines, and is treated as a copy.

Related

performing-cluster-maintenance compared with skills from other repositories

performing-cluster-maintenance next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
performing-cluster-maintenancecockroachdb/claude-pluginSkill428d agoApache-2.0B87Claude Code
designing-application-transactionscockroachdb/cursor-pluginSkill228d agoApache-2.0A102Cursor
auditing-table-statisticscockroachdb/cursor-pluginSkill228d agoApache-2.0A55Cursor
profiling-transaction-fingerprintscockroachdb/cursor-pluginSkill228d agoApache-2.0A80Cursor
configuring-sso-and-scimcockroachdb/cursor-pluginSkill228d agoApache-2.0A91Cursor
designing-multi-region-applicationscockroachdb/cursor-pluginSkill228d agoApache-2.0A89Cursor
analyzing-range-distributioncockroachdb/cursor-pluginSkill228d agoApache-2.0A60Cursor