A command reference for importing bulk data into a Milvus collection through Zilliz Cloud, a managed Milvus service. It also covers import jobs and the temporary stages they reference.

Use it to start, list, and inspect Zilliz Cloud import jobs, or to list, create, and delete import stages.

It avoids having to remember the command names and optional project, cluster, region, and database settings. It provides commands for checking import status and managing stages.

import — Skill for Claude Code and Codex by zilliztech: A command reference for importing bulk data into a…

Install

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.

agentmods

npx agentmods add skills/zilliztech/zilliz-plugin/import

Any agent

npx skills add zilliztech/zilliz-plugin --skill import

Clone the repo

git clone --depth 1 https://github.com/zilliztech/zilliz-plugin

Made for: Claude Code, Codex.

Or install zilliz, the plugin that ships this one along with the rest of its 21 skills, 2 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/zilliztech/zilliz-plugin/import.svg)](https://agentmods.dev/skills/zilliztech/zilliz-plugin/import)

Your own site

<a href="https://agentmods.dev/skills/zilliztech/zilliz-plugin/import"><img src="https://agentmods.dev/badge/skills/zilliztech/zilliz-plugin/import.svg" alt="Measured on agentmods" height="20"></a>

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 853 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00039	$0.00853
Opus 5	$0.00019	$0.00426
Sonnet 5	$0.00008	$0.00171
Haiku 4.5	$0.00004	$0.00085

Measured 4d ago against content hash 7dbd3630fc4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

import 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 4d 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.

plugins/zilliz/skills/import/SKILL.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Prerequisites

CLI installed and logged in (see setup skill).
Target collection must exist on the target cluster.

Commands Reference

Import Jobs

Start an Import Job

zilliz import start --collection <target-collection-name>
# Optional:
#   --cluster-id <target-cluster-id>
#   --project-id <project-id>
#   --region-id <region-id>
# Or use raw JSON: --body '{"files": [["s3://bucket/path/data.parquet"]]}'

List Imports

zilliz import list
# Optional:
#   --cluster-id <cluster-id>
#   --project-id <project-id>
#   --region-id <region-id>
#   --database <database-name>

Check Import Status

zilliz import status --job-id <import-job-id>
# Optional:
#   --cluster-id <cluster-id>
#   --project-id <project-id>
#   --region-id <region-id>

Import Stages

List Stages

zilliz stage list
# Optional: --project-id <filter-by-project-id>
# Pagination: --page-size <n> --page <n>
# Fetch all pages: --all

Create a Stage

zilliz stage create \
  --project-id <owning-project-id> \
  --region-id <cloud-region> \
  --stage-name <stage-name>

Delete a Stage

zilliz stage delete --stage-name <stage-name>

Apply

zilliz stage apply --stage-name <stage-name>
# Optional:
#   --project-id <project-id>
#   --region-id <region-id>
#   --cluster-id <target-cluster-id>
#   --path <stage-subpath>

Integration Setup

Import requires a cloud storage integration to access data files. The integration-id is configured in the Zilliz Cloud console under Project Settings > Integrations. Ensure the integration has read access to the source bucket and path.

Supported file formats: Parquet, JSON, CSV.

Stages vs. Direct Integrations

A stage is a named, project-scoped handle to a pre-uploaded set of files in managed cloud storage. Import jobs reference either:

a customer-owned bucket via an integration (the original flow above), or
a stage (zilliz stage create --project-id <id> --region-id <region> --stage-name <name>), which is preferable when the user wants Zilliz Cloud to host the staging bucket.

Read the full file on GitHub · 120 lines

Changes

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.

4d ago First seen · 120 lines · 39 tokens per session scan A 7dbd3630fc4d

Subscribe to this mod's changes

import is a skill published in the GitHub repository zilliztech/zilliz-plugin (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 853 once invoked, about $0.0002 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.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens