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 m3taz-ahmed/ai-globals --skill search-vector-lordgit clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/search-vector-lord)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/search-vector-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/search-vector-lord/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/m3taz-ahmed/ai-globals/search-vector-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/search-vector-lord.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.00012 | $0.00759 |
| Opus 5.5 | $0.00005 | $0.00304 |
| Sonnet 5.5 | $0.00002 | $0.00152 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
search-vector-lord 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.
What it actually says
[SKILL] search-vector-lord [OBJ] Build full-text and vector retrieval systems for search and RAG. [RULES]
- [CMD] IDs: Elasticsearch
/websites/elastic_co_guide_en_elasticsearch_reference_8_19, OpenSearch/opensearch-project/documentation-website, Meilisearch/websites/meilisearch, pgvector/pgvector/pgvector, Pinecone/websites/pinecone_io, Milvus/milvus-io/milvus-docs. - [REQ] Pillar coverage: full-text search, vector search, hybrid retrieval, schemas/mappings, indexing/ingestion, scaling/operations, observability, security.
- [REQ] Query engine ID with full question + topic (vector search, mapping, indexing, scaling).
- [REQ] Distinguish managed vs self-hosted operational concerns.
- [REQ] RAG designs combine vector + metadata filtering + keyword/rerank unless user asks pure vector.
- [REQ] Retrieval quality is measured: build an eval set (queries + expected hits) BEFORE tuning; track recall@k, MRR, NDCG; every retrieval change is an experiment with a metric, not a hunch.
- [REQ] Hybrid is the default: dense vectors miss exact terms (SKUs, names, error codes); BM25 misses semantics. Combine via RRF or weighted fusion, then a reranker (cross-encoder/Cohere-style) on the top-N for production quality.
- [REQ] Chunking is design: chunk by semantic boundaries (headings, functions, sections) not fixed token windows; overlap ~10-15%; keep chunk metadata (source, section, path, timestamp) — filtering and citations depend on it.
- [REQ] Embeddings are a contract: model choice fixes dimension + index forever — re-embedding = re-indexing. Version the embedding model in the index name; multilingual/domain data may need domain-specific models; eval the model on YOUR data.
- [REQ] Index structure: HNSW params (m, ef_construction, ef_search) are recall-vs-latency levers — tune ef at query time per SLO; filtered search (pre- vs post-filtering) materially changes recall, especially high-selectivity filters.
- [REQ] Full-text specifics: analyzer choice (stemming, synonyms, stopwords) is per-language and per-field; mappings immutable → reindex on change; fuzzy/typo-tolerance tuned (Meilisearch ships it sane; ES needs explicit config).
- [REQ] Metadata filtering: always design filters into the schema (tenant_id, doc_type, date) — post-filtering retrieved results is a recall bug; tenant isolation enforced at query construction, not application hopes.
- [REQ] Freshness & ops: index updates are async (refresh interval, vector index rebuilds) — document staleness windows; monitor index lag, query latency p95, cache hit rates; reindex/rollback plans before schema changes.
- [REQ] RAG answer discipline: retrieved context is untrusted (injection surface); cite chunk sources; relevance threshold below which you say "no answer" rather than hallucinate; context budget allocation (most relevant in, dedupe near-identical chunks).
- [PROHIBIT] Pure-vector search for term-heavy corpora, changing embedding models without reindexing, metadata filtering bolted on after retrieval, unbounded top-k ("k=1000" is a smell), or shipping retrieval without an eval set.
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 Changed · +10 lines 100de7dc6cf2
- 1mo ago First seen · 13 lines · 12 tokens per session scan A 67338acba63d
search-vector-lord is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed 5d ago), licensed MIT. It adds 12 tokens to every session and 759 once invoked, about $0.0000 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-09-03.
Other skills, from other repositories
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.
embeddings
Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support. 75x faster with agentic-flow integration. Use when: semantic search, pattern matching, similarity queries, knowledge retrieval. Skip when: exact text matching, simple lookups, no semantic understanding needed.
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…