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/pipeline-2npx skills add vohongtho/code-intel-platform --skill pipeline-2git 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-2)<a href="https://agentmods.dev/skills/vohongtho/code-intel-platform/pipeline-2"><img src="https://agentmods.dev/badge/skills/vohongtho/code-intel-platform/pipeline-2.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.00054 | $0.00899 |
| Opus 5 | $0.00027 | $0.00449 |
| Sonnet 5 | $0.00011 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
pipeline-2 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pipeline
26 symbols | 9 files | path:
code-intel/core/tests/unit/pipeline/| call density: 0.2/sym
When to Use
Load this skill when:
- The task involves code in
code-intel/core/tests/unit/pipeline/ - The user mentions
execute,extractWithTreeSitter,rawReqor 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/tests/unit/pipeline/parser-corpus.test.ts |
ExpectedSymbol, GoldenFile, ExtractedSymbol, captureKind +(5) |
internal |
code-intel/core/tests/unit/pipeline/graceful-degradation.test.ts |
rawReq, summarize, execute |
internal |
code-intel/core/tests/unit/pipeline/orchestrator.test.ts |
makeContext, makePhase, execute |
internal |
code-intel/core/tests/unit/pipeline/profile.test.ts |
makeContext, makePhase, execute |
internal |
code-intel/core/tests/unit/pipeline/summarize-phase.test.ts |
makeContext, makeFakeProvider, runPhaseWithProvider |
internal |
code-intel/core/tests/unit/pipeline/dag-validator.test.ts |
makePhase, execute |
internal |
code-intel/core/tests/unit/pipeline/incremental-indexer.test.ts |
makeGraph |
internal |
code-intel/core/tests/unit/pipeline/phases.test.ts |
makeContext |
internal |
code-intel/core/tests/unit/pipeline/worker-pool.test.ts |
runOnce |
internal |
Hot Symbols
Sorted by call graph degree (changing these has the highest blast radius):
| Symbol | Kind | In ← | → Out | File |
|---|---|---|---|---|
execute |
method | 12 | 0 | pipeline/profile.test.ts |
extractWithTreeSitter |
function | 1 | 9 | pipeline/parser-corpus.test.ts |
rawReq |
function | 1 | 4 | pipeline/graceful-degradation.test.ts |
extractWithRegex |
function | 1 | 3 | pipeline/parser-corpus.test.ts |
runOnce |
function | 1 | 3 | pipeline/worker-pool.test.ts |
extractSymbols |
function | 1 | 2 | pipeline/parser-corpus.test.ts |
runPhaseWithProvider |
function | 1 | 2 | pipeline/summarize-phase.test.ts |
makeGraph |
function | 1 | 1 | pipeline/incremental-indexer.test.ts |
makeContext |
function | 1 | 1 | pipeline/orchestrator.test.ts |
loadGoldenFiles |
function | 1 | 1 | pipeline/parser-corpus.test.ts |
makeContext |
function | 1 | 1 | pipeline/phases.test.ts |
makeContext |
function | 1 | 1 | pipeline/profile.test.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.
- 3d ago First seen · 68 lines · 54 tokens per session scan A 2d20df9f49b1
pipeline-2 is a skill published in the GitHub repository vohongtho/code-intel-platform (3 stars, last pushed 7d ago), licensed MIT. It adds 54 tokens to every session and 899 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
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
ghttp
The ghttp test HTTP server for testing HTTP clients — NewServer/NewTLSServer, AppendHandlers, the Verify assertions (VerifyRequest/VerifyHeader/VerifyHeaderKV/VerifyJSON/VerifyForm/VerifyBasicAuth/VerifyContentType/VerifyBody), RespondWith/RespondWithJSONEncoded(Ptr), CombineHandlers, RouteToHandler for unordered…
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
gpui-test
Use when writing, debugging, or reproducing GPUI tests in Zed, including gpui::test arguments, TestAppContext parameters, scheduler seeds, ITERATIONS/SEED reproduction, parking failures, and pending task traces.
test-gen
Generate comprehensive unit tests for code files.