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 cb-analytics-querygit 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/cb-analytics-query)<a href="https://agentmods.dev/skills/celticht32/couchbase-skills-for-claude.ai/cb-analytics-query"><img src="https://agentmods.dev/badge/skills/celticht32/couchbase-skills-for-claude.ai/cb-analytics-query/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/cb-analytics-query"><img src="https://agentmods.dev/badge/skills/celticht32/couchbase-skills-for-claude.ai/cb-analytics-query.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.00112 | $0.02540 |
| Opus 5.5 | $0.00045 | $0.01016 |
| Sonnet 5.5 | $0.00022 | $0.00508 |
| Haiku 4.5 | $0.00011 | $0.00254 |
Grade A, and why
cb-analytics-query 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cb-analytics-query — 92% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Querying Couchbase Analytics via cb-analytics-mcp
You have five SQL++ tools for talking to the Analytics service. Picking the right one matters — they have different cost profiles, rate-limit budgets, and result shapes.
| Tool | Cost | Result shape | When to reach for it |
|---|---|---|---|
execute_query |
high (full result) | rows, may be truncated | DDL, mutations, small SELECTs |
execute_query_readonly |
high (full result), cached | rows, may be truncated, cached: bool |
repeated SELECTs in an investigation loop |
execute_query_paginated |
constant per page | first page + handle | SELECTs that might return many rows |
fetch_next_page |
constant per page | next page for a handle | follow-up to paginated |
explain_query |
tiny (no execution) | query plan | "why is this slow" |
The cardinal rule: pick the tool that matches what you'll do with the result
If you only need the first N rows to answer the user's question, use
execute_query_paginated with page_size=N. Don't pull a million rows
through the MCP boundary just to take the first 20.
If you need to show the user the data (and the dataset is small),
execute_query_readonly is fine — but watch for truncated: true in the
response.
If you need to make a decision based on aggregates (COUNT, SUM,
AVG, GROUP BY), the result is small by construction. Use
execute_query_readonly and benefit from the cache.
The soft cap (you will see truncated: true)
Both execute_query and execute_query_readonly enforce a server-side row
cap (default 1000, configurable via MAX_QUERY_ROWS). Responses include:
truncated: trueif the cap kicked inrow_cap: the cap that was applied (ornullif disabled)full_row_count: how many rows the cluster actually had
When you see truncated: true, do not silently report incomplete data.
Either:
- Tell the user the result is truncated and ask if they want all rows (then re-issue as paginated), or
- If you only needed a sample, acknowledge it and continue ("here are the first 1000 of 47,832 matching rows").
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.
- 1mo ago First seen · 255 lines · 112 tokens per session scan A 8e22f20f2410
cb-analytics-query is a skill published in the GitHub repository celticht32/Couchbase-Skills-for-Claude.ai (4 stars, last pushed 3mo ago), licensed MIT. It adds 112 tokens to every session and 2,540 once invoked, about $0.0004 per session on Opus 5.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.
elasticsearch-best-practices
Elasticsearch development best practices for indexing, querying, and search optimization.
kysely
Guidelines for developing with Kysely, a type-safe TypeScript SQL query builder with autocompletion support.
drizzle-orm
Guidelines for developing with Drizzle ORM, a lightweight type-safe TypeScript ORM with SQL-like syntax.
mysql-best-practices
MySQL development best practices for schema design, query optimization, and database administration.
postgresql-best-practices
PostgreSQL development best practices for schema design, query optimization, and database administration.