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/multi-reponpx skills add vohongtho/code-intel-platform --skill multi-repogit clone --depth 1 https://github.com/vohongtho/code-intel-platformWrote 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/vohongtho/code-intel-platform/multi-repo)<a href="https://agentmods.dev/skills/vohongtho/code-intel-platform/multi-repo"><img src="https://agentmods.dev/badge/skills/vohongtho/code-intel-platform/multi-repo.svg" alt="Measured on agentmods" 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 | $0.00055 | $0.01195 |
| Opus 5 | $0.00028 | $0.00598 |
| Sonnet 5 | $0.00011 | $0.00239 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
multi-repo 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 3d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
multi-repo
41 symbols | 10 files | path:
code-intel/core/src/multi-repo/| call density: 0.6/sym
When to Use
Load this skill when:
- The task involves code in
code-intel/core/src/multi-repo/ - The user mentions
mergeSearchResults,listGroups,getGroupor asks how they work - Adding, modifying, or debugging multi-repo-related functionality
- Tracing call chains that pass through the multi-repo layer
Key Files
| File | Symbols | Notes |
|---|---|---|
code-intel/core/src/multi-repo/group-registry.ts |
groupFile, loadGroup, saveGroup, listGroups +(6) |
9 exported |
code-intel/core/src/multi-repo/workspace-detector.ts |
WorkspacePackage, WorkspaceInfo, expandGlob, resolvePackages +(2) |
4 exported |
code-intel/core/src/multi-repo/type-similarity.ts |
normalizeType, paramTypeSimilarity, returnTypeSimilarity, paramCountSimilarity +(1) |
4 exported |
code-intel/core/src/multi-repo/types.ts |
GroupMember, RepoGroup, Contract, ContractLink +(1) |
5 exported |
code-intel/core/src/multi-repo/group-manager.ts |
listGroups, getGroup, createGroup, deleteGroup |
4 exported |
code-intel/core/src/multi-repo/group-config.ts |
RepoGroup, loadGroupConfig, saveGroupConfig |
3 exported |
code-intel/core/src/multi-repo/group-sync.ts |
extractContracts, matchContracts, syncGroup |
1 exported |
code-intel/core/src/multi-repo/graph-from-db.ts |
parseRow, loadGraphFromDB |
1 exported |
code-intel/core/src/multi-repo/group-query.ts |
GroupQueryResult, queryGroup |
2 exported |
code-intel/core/src/multi-repo/cross-repo-search.ts |
mergeSearchResults |
1 exported |
Entry Points
Start exploration here — exported symbols with no external callers:
mergeSearchResults(function)→code-intel/core/src/multi-repo/cross-repo-search.ts:4listGroups(function)→code-intel/core/src/multi-repo/group-manager.ts:8getGroup(function)→code-intel/core/src/multi-repo/group-manager.ts:21createGroup(function)→code-intel/core/src/multi-repo/group-manager.ts:30deleteGroup(function)→code-intel/core/src/multi-repo/group-manager.ts:35listGroups(function)→code-intel/core/src/multi-repo/group-registry.ts:29
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.
- 3d ago First seen · 80 lines · 55 tokens per session scan A a3d8e90d294a
multi-repo is a skill published in the GitHub repository vohongtho/code-intel-platform (3 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,195 once invoked, about $0.0003 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…