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-ftsgit 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-fts)<a href="https://agentmods.dev/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-fts"><img src="https://agentmods.dev/badge/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-fts/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-fts"><img src="https://agentmods.dev/badge/skills/celticht32/couchbase-skills-for-claude.ai/couchbase-fts.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.00208 | $0.01646 |
| Opus 5 | $0.00104 | $0.00823 |
| Sonnet 5 | $0.00042 | $0.00329 |
| Haiku 4.5 | $0.00021 | $0.00165 |
Grade A, and why
couchbase-fts 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Couchbase Full Text Search & Vector Search
A skill for designing and operating Couchbase FTS and vector search indexes. Distinct from:
couchbase-sqlpp-tuning— SQL++ / GSI index design (not Search service)couchbase-data-modeling— document shape decisions that affect what FTS can indexcouchbase-mcp— calling the actualcb_fts_search,admin_fts_*, andadmin_vector_index_*tools
If the conversation is "I need to search text / find similar documents / search by location," this is the right skill.
When this skill applies
- "How do I do full-text search in Couchbase?"
- "How do I build an FTS index?"
- "Why isn't my FTS query matching what I expect?"
- "How do I add fuzzy / wildcard / phrase search?"
- "How do I search by geo-distance?"
- "How do I implement vector / semantic / kNN search?"
- "How do I combine text search with vector search (hybrid)?"
- "What analyzer should I use for [language]?"
- "How do I boost certain fields?"
- "What are FTS synonyms and when should I use them?"
- "How do I size FTS / vector index memory?"
Pick the right reference
| Question | Read |
|---|---|
| "How do I design an FTS index — mappings, analyzers, type fields?" | references/index-design.md |
| "How do I write FTS queries — match, phrase, fuzzy, wildcard, conjunction, geo?" | references/query-types.md |
| "Analyzers, tokenizers, token filters — how do they work, which to pick?" | references/analyzers.md |
| "Vector search — kNN, hybrid search, index design for embeddings?" | references/vector-search.md |
| "FTS synonyms (8.x) — what they are, how to create, when to use?" | references/synonyms.md |
| "FTS is slow / results are wrong / index not updating — how to debug?" | references/troubleshooting.md |
Three core principles
Principle 1 — The index definition determines everything. FTS doesn't infer what to index from the document. If a field isn't mapped (or dynamic mapping is off), FTS ignores it. Get the index definition right before debugging queries. The most common FTS failure mode is "the field isn't indexed."
What ships with it
6 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 · 89 lines · 208 tokens per session scan A d79b560be5ed
couchbase-fts is a skill published in the GitHub repository celticht32/Couchbase-Skills-for-Claude.ai (4 stars, last pushed 2mo ago), licensed MIT. It adds 208 tokens to every session and 1,646 once invoked, about $0.0010 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
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…
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.
pinecone
Managed vector database for production AI applications. Fully managed, auto-scaling, with hybrid search (dense + sparse), metadata filtering, and namespaces. Low latency (<100ms p95). Use for production RAG, recommendation systems, or semantic search at scale. Best for serverless, managed infrastructure.
qdrant
Vector search engine for production RAG systems.
chroma
Embedding database for RAG and semantic search.
pinecone
Managed vector DB for production RAG and search.