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-transactionsgit 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-transactions)<a href="https://agentmods.dev/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-transactions"><img src="https://agentmods.dev/badge/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-transactions/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-transactions"><img src="https://agentmods.dev/badge/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-transactions.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.00156 | $0.00699 |
| Opus 5 | $0.00078 | $0.00349 |
| Sonnet 5 | $0.00031 | $0.00140 |
| Haiku 4.5 | $0.00016 | $0.00070 |
Grade A, and why
couchbase-transactions 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Couchbase Distributed Transactions
A skill for designing and implementing multi-document ACID transactions in Couchbase. Goes deeper than the overview in couchbase-app-integration/references/transactions-app-side.md.
Distinct from:
couchbase-app-integration— general SDK patterns; has a transactions overview but not the depth needed for production transaction designcouchbase-mcp— thecb_transaction_runtool for running transactions via the MCP server
When this skill applies
- "How do I atomically update multiple documents?"
- "How do transactions work under the hood?"
- "My transaction is retrying — why?"
- "How do I handle a transaction conflict?"
- "What happens if the client crashes mid-transaction?"
- "Transactions are slow — how do I tune them?"
- "What are ATRs and why does my bucket have them?"
- "How do I model data to minimize transaction use?"
Pick the right reference
| Question | Read |
|---|---|
| "When should I use transactions vs single-doc ops vs subdoc?" | references/when-to-use.md |
| "How do they work? ATRs, two-phase commit, retry, expiry" | references/mechanics.md |
| "Code patterns — Python, Java, Node; error handling; retry logic" | references/patterns.md |
Core principle: try to design around transactions
Transactions in Couchbase are meaningfully slower than equivalent single-document KV operations — they do substantially more work (staging, two-phase commit across documents, Active Transaction Record bookkeeping, and possible retries) — and add retry complexity. Before reaching for a transaction, ask: can this be modeled as a single-document update? Often the answer is yes. See references/when-to-use.md for the decision framework.
When you do need transactions, they're correct and reliable — just plan for the cost.
Quick tool map
| Task | Tool |
|---|---|
| Run a transaction via MCP | cb_transaction_run |
| Single-document atomic op (no transaction needed) | cb_mutate_in |
| Check for orphaned ATR documents | cb_query on _txn:atr-* keys |
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.
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 · 53 lines · 156 tokens per session scan A ae66672e86c6
couchbase-transactions is a skill published in the GitHub repository celticht32/Couchbase-Skills-for-Claude.ai (4 stars, last pushed 2mo ago), licensed MIT. It adds 156 tokens to every session and 699 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.