Borrowing it
Nothing to install: this file belongs to vohongtho/code-intel-platform. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vohongtho/code-intel-platform/main/.claude/skills/code-intel/pipeline/SKILL.mdgit 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/pipeline)<a href="https://agentmods.dev/skills/vohongtho/code-intel-platform/pipeline"><img src="https://agentmods.dev/badge/skills/vohongtho/code-intel-platform/pipeline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vohongtho/code-intel-platform/pipeline"><img src="https://agentmods.dev/badge/skills/vohongtho/code-intel-platform/pipeline.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00059 | $0.01051 |
| Opus 5.5 | $0.00024 | $0.00420 |
| Sonnet 5.5 | $0.00012 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
pipeline 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 1mo 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pipeline
30 symbols | 6 files | path:
code-intel/core/src/pipeline/| call density: 0.2/sym
When to Use
Load this skill when:
- The task involves code in
code-intel/core/src/pipeline/ - The user mentions
constructor,isWatching,lastEventAtor asks how they work - Adding, modifying, or debugging pipeline-related functionality
- Tracing call chains that pass through the pipeline layer
Key Files
| File | Symbols | Notes |
|---|---|---|
code-intel/core/src/pipeline/file-watcher.ts |
FileWatcherOptions, FileWatcher, constructor, isWatching +(5) |
9 exported |
code-intel/core/src/pipeline/incremental.ts |
getCurrentCommitHash, getChangedFilesSince, filterChangedByMtime, buildMtimeSnapshot +(2) |
6 exported |
code-intel/core/src/pipeline/incremental-indexer.ts |
PatchResult, IncrementalIndexer, constructor, patchGraph +(1) |
5 exported |
code-intel/core/src/pipeline/dag-validator.ts |
ValidationError, validateDAG, dfs, topologicalSort |
4 exported |
code-intel/core/src/pipeline/orchestrator.ts |
PipelineRunResult, runPipeline, runPhase |
3 exported |
code-intel/core/src/pipeline/types.ts |
PhaseResult, PipelineContext, Phase |
3 exported |
Entry Points
Start exploration here — exported symbols with no external callers:
constructor(method)→code-intel/core/src/pipeline/file-watcher.ts:43isWatching(method)→code-intel/core/src/pipeline/file-watcher.ts:49lastEventAt(method)→code-intel/core/src/pipeline/file-watcher.ts:53start(method)→code-intel/core/src/pipeline/file-watcher.ts:58handle(function)→code-intel/core/src/pipeline/file-watcher.ts:70stop(method)→code-intel/core/src/pipeline/file-watcher.ts:93
Hot Symbols
Sorted by call graph degree (changing these has the highest blast radius):
| Symbol | Kind | In ← | → Out | File |
|---|---|---|---|---|
patchGraph |
method | 2 | 20 | pipeline/incremental-indexer.ts |
runPipeline |
function | 10 | 7 | pipeline/orchestrator.ts |
decideIncremental |
function | 2 | 9 | pipeline/incremental.ts |
dfs |
function | 1 | 4 | pipeline/dag-validator.ts |
handle |
function | 0 | 5 | pipeline/file-watcher.ts |
validateDAG |
function | 2 | 2 | pipeline/dag-validator.ts |
topologicalSort |
function | 2 | 2 | pipeline/dag-validator.ts |
start |
method | 0 | 4 | pipeline/file-watcher.ts |
stop |
method | 0 | 3 | pipeline/file-watcher.ts |
filterChangedByMtime |
function | 2 | 1 | pipeline/incremental.ts |
buildMtimeSnapshot |
function | 2 | 1 | pipeline/incremental.ts |
runPhase |
function | 0 | 3 | pipeline/orchestrator.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.
- 1mo ago First seen · 81 lines · 59 tokens per session scan A 1e09f561eac5
pipeline is a skill published in the GitHub repository vohongtho/code-intel-platform (3 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,051 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…