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/vohongtho/code-intel-platform/searchnpx skills add vohongtho/code-intel-platform --skill searchgit clone --depth 1 https://github.com/vohongtho/code-intel-platformWhat 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.00048 | $0.00955 |
| Opus 5 | $0.00024 | $0.00477 |
| Sonnet 5 | $0.00010 | $0.00191 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
search
45 symbols | 5 files | path:
code-intel/core/src/search/| call density: 0.6/sym
When to Use
Load this skill when:
- The task involves code in
code-intel/core/src/search/ - The user mentions
constructor,isLoaded,searchor asks how they work - Adding, modifying, or debugging search-related functionality
- Tracing call chains that pass through the search layer
Key Files
| File | Symbols | Notes |
|---|---|---|
code-intel/core/src/search/bm25-index.ts |
PostingEntry, NodeMeta, tokenize, nodeToDoc +(13) |
10 exported |
code-intel/core/src/search/vector-index.ts |
CachedRow, VectorIndex, constructor, init +(11) |
9 exported |
code-intel/core/src/search/text-search.ts |
SearchResult, textSearch, isTestPath, isDistPath +(1) |
5 exported |
code-intel/core/src/search/embedder.ts |
EmbeddedNode, getEmbedder, embedNodes, buildText |
4 exported |
code-intel/core/src/search/hybrid-search.ts |
HybridSearchOptions, HybridSearchResult, hybridSearch, runVectorSearch |
3 exported |
Entry Points
Start exploration here — exported symbols with no external callers:
constructor(method)→code-intel/core/src/search/bm25-index.ts:128isLoaded(method)→code-intel/core/src/search/bm25-index.ts:130search(method)→code-intel/core/src/search/bm25-index.ts:275hybridSearch(function)→code-intel/core/src/search/hybrid-search.ts:26isTestPath(function)→code-intel/core/src/search/text-search.ts:21isDistPath(function)→code-intel/core/src/search/text-search.ts:23
Hot Symbols
Sorted by call graph degree (changing these has the highest blast radius):
| Symbol | Kind | In ← | → Out | File |
|---|---|---|---|---|
build |
method | 5 | 11 | search/bm25-index.ts |
updateNodes |
method | 2 | 14 | search/bm25-index.ts |
load |
method | 6 | 9 | search/bm25-index.ts |
embedNodes |
function | 2 | 7 | search/embedder.ts |
runVectorSearch |
function | 1 | 8 | search/hybrid-search.ts |
reciprocalRankFusion |
function | 5 | 3 | search/text-search.ts |
search |
method | 0 | 7 | search/bm25-index.ts |
textSearch |
function | 7 | 0 | search/text-search.ts |
Bm25Index |
class | 6 | 0 | search/bm25-index.ts |
setCached |
method | 1 | 5 | search/bm25-index.ts |
hybridSearch |
function | 0 | 6 | search/hybrid-search.ts |
buildIndex |
method | 3 | 3 | search/vector-index.ts |
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 · 75 lines · 48 tokens per session scan A 08e7736b7051
search is a skill published in the GitHub repository vohongtho/code-intel-platform (3 stars, last pushed 6d ago), licensed MIT. It adds 48 tokens to every session and 955 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-08-31.
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…