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 agentmods add skills/secondlifes/code-intel/hybrid-searchnpx skills add SecondLifes/code-intel --skill hybrid-searchgit clone --depth 1 https://github.com/SecondLifes/code-intelWhat 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 | $0.00065 | $0.00768 |
| Opus 5 | $0.00032 | $0.00384 |
| Sonnet 5 | $0.00013 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
qdrant-hybrid-search 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 2d 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.
This is a copy
94% identical to qdrant-hybrid-search — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hybrid Search in Qdrant
Hybrid search means running two or more different searches in parallel and combining their results into one.
In Qdrant this is powered by the Query API via prefetch: each prefetch runs exactly one type of search independently, and the outer query combines results from parallel prefetches.
Prefetches can be nested and searches can be multi-stage, all pipeline happening in one request through Query API. See Universal Query API for examples.
Identify the user's problem and pick building blocks:
- What can go into one prefetch, e.g. power one search, in Search Types
- How to combine results of these searches (RRF, DBSF, FormulaQuery, reranking) in Combining Searches
Based on what you've picked, test your approach:
- Configure Qdrant collection with named vectors, where each named vector usually corresponds to one representation (different embedding models or different vector types) of a data point.
- Construct a hybrid search request with Query API from your building blocks. You can search independently among one type of vectors, with
prefetch+using, like shown in examples in Hybrid Queries documentation. - Evaluate hybrid search quality on real user data and provide user with improvements and tradeoffs (speed/resources).
How Isolated Are Parallel Searches?
Use when: different tenants share one collection and you need to understand hybrid search isolation guarantees.
If user wants to isolate/share hybrid search pipelines between tenants, consider that:
- Indexes (sparse, payload and dense) and IDF modifier for sparse vectors are computed independently per shard, not per tenant, by default — payload-based tenant partitioning alone does not isolate IDF statistics. On Qdrant 1.19 or newer, the
idfsearch param can scope IDF statistics to a payload-filtered corpus (requires a payload index on the filtered field), giving each tenant properly isolated BM25 scoring instead of shard-wide statistics. - Prefetch runs independently per shard to retrieve #limit results, so for collection-level prefetches if collection has several shards, Qdrant will always prefetch under the hood #limit * #shard results. Final results are merged based on scores.
- In nested prefetches (deeper than 1 level), methods described in "Combining Searches" might be done on a shard level first, then per-shards results once again will be merged based on scores.
What ships with it
2 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.
- 2d ago First seen · 39 lines · 65 tokens per session scan A 9985b2a228ea
qdrant-hybrid-search is a skill published in the GitHub repository SecondLifes/code-intel (2 stars, last pushed 22d ago), licensed Apache-2.0. It adds 65 tokens to every session and 768 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to qdrant-hybrid-search, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…