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/phasesnpx skills add vohongtho/code-intel-platform --skill phasesgit 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.00058 | $0.01028 |
| Opus 5 | $0.00029 | $0.00514 |
| Sonnet 5 | $0.00012 | $0.00206 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
phases 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 yesterday.
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.
phases
38 symbols | 6 files | path:
code-intel/core/src/pipeline/phases/| call density: 0.7/sym
When to Use
Load this skill when:
- The task involves code in
code-intel/core/src/pipeline/phases/ - The user mentions
execute,execute,executeor asks how they work - Adding, modifying, or debugging phases-related functionality
- Tracing call chains that pass through the phases layer
Key Files
| File | Symbols | Notes |
|---|---|---|
code-intel/core/src/pipeline/phases/parse-phase.ts |
isDefCapture, captureKind, isExported, Param +(16) |
1 exported |
code-intel/core/src/pipeline/phases/resolve-phase.ts |
ParsedImport, ParsedCall, ParsedHeritage, execute +(4) |
1 exported |
code-intel/core/src/pipeline/phases/summarize-phase.ts |
buildPrompt, codeHash, trimSnippet, createSummarizePhase +(1) |
2 exported |
code-intel/core/src/pipeline/phases/scan-phase.ts |
loadIgnorePatterns, execute, walk |
2 exported |
code-intel/core/src/pipeline/phases/cluster-phase.ts |
execute |
1 exported |
code-intel/core/src/pipeline/phases/flow-phase.ts |
execute |
1 exported |
Entry Points
Start exploration here — exported symbols with no external callers:
execute(method)→code-intel/core/src/pipeline/phases/cluster-phase.ts:7execute(method)→code-intel/core/src/pipeline/phases/flow-phase.ts:7execute(method)→code-intel/core/src/pipeline/phases/parse-phase.ts:460execute(method)→code-intel/core/src/pipeline/phases/resolve-phase.ts:37execute(method)→code-intel/core/src/pipeline/phases/summarize-phase.ts:40
Hot Symbols
Sorted by call graph degree (changing these has the highest blast radius):
| Symbol | Kind | In ← | → Out | File |
|---|---|---|---|---|
extractFromTree |
function | 1 | 19 | phases/parse-phase.ts |
execute |
method | 0 | 16 | phases/parse-phase.ts |
execute |
method | 0 | 16 | phases/resolve-phase.ts |
execute |
method | 0 | 16 | phases/summarize-phase.ts |
execute |
method | 0 | 10 | phases/cluster-phase.ts |
execute |
method | 0 | 10 | phases/flow-phase.ts |
extractWithRegex |
function | 1 | 7 | phases/parse-phase.ts |
isExported |
function | 5 | 0 | phases/parse-phase.ts |
execute |
method | 1 | 4 | phases/scan-phase.ts |
extractFromTreeAsync |
function | 1 | 3 | phases/parse-phase.ts |
createSummarizePhase |
function | 4 | 0 | phases/summarize-phase.ts |
extractParams |
function | 1 | 2 | phases/parse-phase.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.
- yesterday First seen · 80 lines · 58 tokens per session scan A a6c81d2ccad8
phases is a skill published in the GitHub repository vohongtho/code-intel-platform (3 stars, last pushed 6d ago), licensed MIT. It adds 58 tokens to every session and 1,028 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.