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 LuuOW/meridian-mcp --skill vector-storegit clone --depth 1 https://github.com/LuuOW/meridian-mcpWrote 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/luuow/meridian-mcp/vector-store)<a href="https://agentmods.dev/skills/luuow/meridian-mcp/vector-store"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/vector-store/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/luuow/meridian-mcp/vector-store"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/vector-store.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.00034 | $0.02076 |
| Opus 5 | $0.00017 | $0.01038 |
| Sonnet 5 | $0.00007 | $0.00415 |
| Haiku 4.5 | $0.00003 | $0.00208 |
Grade A, and why
vector-store 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 5d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vector-store
Covers production use of Qdrant as a vector database: collection lifecycle, batch upserts, hybrid search, payload filtering, snapshot management, and multi-tenant patterns.
1) Collection lifecycle
from qdrant_client import QdrantClient
from qdrant_client.models import (
Distance, VectorParams, OptimizersConfigDiff,
HnswConfigDiff, PayloadSchemaType, QuantizationConfig,
ScalarQuantizationConfig, ScalarType,
)
qdrant = QdrantClient(host="localhost", port=6333)
def create_collection(name: str, dim: int = 1536, on_disk: bool = True):
qdrant.recreate_collection(
collection_name=name,
vectors_config=VectorParams(size=dim, distance=Distance.COSINE, on_disk=on_disk),
hnsw_config=HnswConfigDiff(m=16, ef_construct=200, full_scan_threshold=10_000),
optimizers_config=OptimizersConfigDiff(indexing_threshold=20_000),
on_disk_payload=on_disk,
)
# Index frequently-filtered payload fields
for field in ("domain", "type", "published_at"):
qdrant.create_payload_index(name, field, PayloadSchemaType.KEYWORD)
def delete_collection(name: str):
qdrant.delete_collection(name)
def collection_info(name: str) -> dict:
info = qdrant.get_collection(name)
return {
"points": info.points_count,
"vectors": info.vectors_count,
"status": info.status,
"segments": info.segments_count,
}
2) Batch upsert patterns
from qdrant_client.models import PointStruct, UpdateStatus
import uuid, hashlib
def doc_id_to_uuid(doc_id: str) -> str:
"""Deterministic UUID from string ID — Qdrant accepts UUIDs."""
return str(uuid.UUID(bytes=hashlib.md5(doc_id.encode()).digest()))
async def upsert_batch(
collection: str,
documents: list[dict], # each: {"id": str, "text": str, "payload": dict}
embed_fn, # async (list[str]) -> list[list[float]]
batch_size: int = 100,
) -> int:
total = 0
for i in range(0, len(documents), batch_size):
batch = documents[i : i + batch_size]
texts = [d["text"] for d in batch]
vectors = await embed_fn(texts)
points = [
PointStruct(
id=doc_id_to_uuid(d["id"]),
vector=vec,
payload={**d["payload"], "text": d["text"], "_doc_id": d["id"]},
)
for d, vec in zip(batch, vectors)
]
result = qdrant.upsert(collection_name=collection, points=points, wait=True)
assert result.status == UpdateStatus.COMPLETED
total += len(points)
return total
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.
- 5d ago First seen · 244 lines · 34 tokens per session scan A 145f4277de2f
vector-store is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 2,076 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
vector-backend-operations
Select and connect the right vector-store backend for the vector-mcp MCP server — chromadb, postgres/pgvector, qdrant, couchbase, or mongodb — and supply the correct dbtype/connection parameters that every collection and search call needs. Use when the agent must decide which engine to target, wire up…
vector-hybrid-search
Retrieve knowledge from a vector-store collection via the vector-mcp MCP server's vectorsearch tool — semantic (ANN) search, lexical BM25 search, or a hybrid of the two fused with Reciprocal Rank Fusion. Use when the agent must answer a question from an indexed corpus, pull top-k relevant chunks for RAG context, or…
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.
global-utils-knowledge
Domain knowledge for the globalutils shared Python library. Provides cross-service utilities: config, Redis, ports, helpers, embedding, Flask, and Celery app setup. Use when working on files under globalutils/.
vector-db-ops
Use when vector database operations — Pinecone, Weaviate, Qdrant, ChromaDB. Indexing, querying, filtering, and managing vector embeddings for RAG and similarity search. Use when working with vector db ops.
vector-search-workflows
Vector search indexing and querying workflows using MCP Vector Search, including setup, reindexing, auto-index strategies, and MCP integration.