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/getklai/klai/codeindex-exploringnpx skills add GetKlai/klai --skill codeindex-exploringgit clone --depth 1 https://github.com/GetKlai/klaiWhat 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.00054 | $0.00734 |
| Opus 5 | $0.00027 | $0.00367 |
| Sonnet 5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
codeindex-exploring 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploring Codebases with CodeIndex
When to Use
- "How does authentication work?"
- "What's the project structure?"
- "Show me the main components"
- "Where is the database logic?"
- Understanding code you haven't seen before
Workflow
1. READ codeindex://repos → Discover indexed repos
2. READ codeindex://repo/{name}/context → Codebase overview, check staleness
3. codeindex_query({query: "<what you want to understand>"}) → Find related execution flows
4. codeindex_context({name: "<symbol>"}) → Deep dive on specific symbol
5. READ codeindex://repo/{name}/process/{name} → Trace full execution flow
In Conductor worktrees, "Index is stale" can be an overlay/canonical-checkout mismatch. Use
scripts/codeindex-health.sh; only runscripts/codeindex-health.sh --repairwhen it reports the shared base index is stale. Verify branch-local code with source files/diffs.
Checklist
- [ ] READ codeindex://repo/{name}/context
- [ ] codeindex_query for the concept you want to understand
- [ ] Review returned processes (execution flows)
- [ ] codeindex_context on key symbols for callers/callees
- [ ] READ process resource for full execution traces
- [ ] Read source files for implementation details
Resources
| Resource | What you get |
|---|---|
codeindex://repo/{name}/context |
Stats, staleness warning (~150 tokens) |
codeindex://repo/{name}/clusters |
All functional areas with cohesion scores (~300 tokens) |
codeindex://repo/{name}/cluster/{name} |
Area members with file paths (~500 tokens) |
codeindex://repo/{name}/process/{name} |
Step-by-step execution trace (~200 tokens) |
Tools
codeindex_query — find execution flows related to a concept:
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 · 82 lines · 54 tokens per session scan A e551e5961789
codeindex-exploring is a skill published in the GitHub repository GetKlai/klai (11 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 734 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-30.
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…