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 skills add celticht32/Couchbase-Skills-for-Claude.ai --skill couchbase-upgradegit clone --depth 1 https://github.com/celticht32/Couchbase-Skills-for-Claude.aiWrote 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/celticht32/couchbase-skills-for-claude.ai/couchbase-upgrade)<a href="https://agentmods.dev/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-upgrade"><img src="https://agentmods.dev/badge/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-upgrade/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/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-upgrade"><img src="https://agentmods.dev/badge/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-upgrade.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.00169 | $0.01498 |
| Opus 5 | $0.00084 | $0.00749 |
| Sonnet 5 | $0.00034 | $0.00300 |
| Haiku 4.5 | $0.00017 | $0.00150 |
Grade A, and why
couchbase-upgrade 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 12d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Couchbase Upgrade
Planning and executing Couchbase Server version upgrades — upgrade paths, breaking changes, pre/post-upgrade steps, and 8.0-specific considerations.
Distinct from the rolling upgrade section in couchbase-mcp (which covers the MCP tool sequence for executing the upgrade). This skill covers the planning layer: what to check before you run those tools.
When this skill applies
- "How do I upgrade from 7.x to 8.0?"
- "What changed in 8.0 that could break my cluster?"
- "What's the safe upgrade path?"
- "How do I verify the upgrade worked?"
- "What's the cluster compatibility version?"
- "Do I need EE for 8.0 defaults?"
Supported upgrade paths
Couchbase supports upgrading one major version at a time:
| From | To | Supported |
|---|---|---|
| 7.0 / 7.1 / 7.2 / 7.6 | 8.0 | Yes — rolling upgrade |
| 6.x | 8.0 | No — must go through 7.x first |
| Community Edition | Enterprise Edition | Requires reinstall, not in-place upgrade |
Always upgrade to the latest patch of your current version before upgrading to the next major version. Bugs fixed in patch releases can affect the upgrade process itself.
Pre-upgrade checklist
- Full cluster backup (cbbackupmgr or Capella managed backup)
- Verify current cluster is healthy: all nodes
active+healthy, rebalance not in progress, XDCR caught up (changes_left≈ 0) - Review breaking changes for the target version (see below for 8.0)
- Test the upgrade on a staging cluster first
- Check SDK compatibility: ensure your SDK versions support the target Couchbase version
- Read the release notes for your specific patch version
Couchbase 8.0 breaking changes
1. Magma storage engine is the new default (EE only)
New buckets created on 8.0 EE use Magma with 128 vBuckets by default, instead of the previous Couchbase storage engine with 1024 vBuckets.
Impact:
- Existing buckets are not changed — they keep their current storage engine and vBucket count
- New buckets created after upgrade will use Magma 128 vBuckets unless you specify otherwise
- If your deployment scripts create buckets with hardcoded assumptions about 1024 vBuckets, update them
- If you need 1024 vBuckets for compatibility reasons, explicitly set
numVBuckets=1024andstorageBackend=couchstorewhen creating new buckets post-upgrade
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.
- 12d ago First seen · 125 lines · 169 tokens per session scan A a97fa3d754fa
couchbase-upgrade is a skill published in the GitHub repository celticht32/Couchbase-Skills-for-Claude.ai (4 stars, last pushed 2mo ago), licensed MIT. It adds 169 tokens to every session and 1,498 once invoked, about $0.0008 per session on Opus 5. 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 skills, from other repositories
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms.
chroma
Open-source embedding database for AI applications. Store embeddings and metadata, perform vector and full-text search, filter by metadata. Simple 4-function API. Scales from notebooks to production clusters. Use for semantic search, RAG applications, or document retrieval. Best for local development and open-source…
db-seed
Generate database seed scripts with realistic sample data. Reads Drizzle schemas or SQL migrations, respects foreign key ordering, produces idempotent TypeScript or SQL seed files. Handles D1 batch limits, unique constraints, and domain-appropriate data. Use when populating dev/demo/test databases. Triggers: 'seed…
d1-drizzle-schema
Generate Drizzle ORM schemas for Cloudflare D1 databases with correct D1-specific patterns. Produces schema files, migration commands, type exports, and DATABASESCHEMA.md documentation. Handles D1 quirks: foreign keys always enforced, no native BOOLEAN/DATETIME types, 100 bound parameter limit, JSON stored as TEXT.…
d1-migration
Cloudflare D1 migration workflow: generate with Drizzle, inspect SQL for gotchas, apply to local and remote, fix stuck migrations, handle partial failures. Use when running migrations, fixing migration errors, or setting up D1 schemas.
qdrant-vector-search
High-performance vector similarity search engine for RAG and semantic search. Use when building production RAG systems requiring fast nearest neighbor search, hybrid search with filtering, or scalable vector storage with Rust-powered performance.