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 skills add zilliztech/zilliz-plugin --skill importgit clone --depth 1 https://github.com/zilliztech/zilliz-pluginWrote 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/zilliztech/zilliz-plugin/import)<a href="https://agentmods.dev/skills/zilliztech/zilliz-plugin/import"><img src="https://agentmods.dev/badge/skills/zilliztech/zilliz-plugin/import/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/zilliztech/zilliz-plugin/import"><img src="https://agentmods.dev/badge/skills/zilliztech/zilliz-plugin/import.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.00039 | $0.00853 |
| Opus 5.5 | $0.00016 | $0.00341 |
| Sonnet 5.5 | $0.00008 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00085 |
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 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 — 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.
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 · 120 lines · 39 tokens per session scan A 7dbd3630fc4d
import is a skill published in the GitHub repository zilliztech/zilliz-plugin (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 853 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-30.
Other skills, from other repositories
cloudflare-vectorize
Cloudflare Vectorize vector database for semantic search and RAG. Use for vector indexes, embeddings, similarity search, or encountering dimension mismatches, filter errors.
chroma
Open-source embedding database for AI applications. Store embeddings and metadata, perform vector and full-text search, filter by metadata. Simple 4-function API. Scales from notebooks to production clusters. Use for semantic search, RAG applications, or document retrieval. Best for local development and open-source…
pinecone
Managed vector database for production AI applications. Fully managed, auto-scaling, with hybrid search (dense + sparse), metadata filtering, and namespaces. Low latency (<100ms p95). Use for production RAG, recommendation systems, or semantic search at scale. Best for serverless, managed infrastructure.
chroma
Open-source embedding database for AI applications. Store embeddings and metadata, perform vector and full-text search, filter by metadata. Simple 4-function API. Scales from notebooks to production clusters. Use for semantic search, RAG applications, or document retrieval. Best for local development and open-source…
chroma
Open-source embedding database for AI applications. Store embeddings and metadata, perform vector and full-text search, filter by metadata. Simple 4-function API. Scales from notebooks to production clusters. Use for semantic search, RAG applications, or document retrieval. Best for local development and open-source…
pinecone
Managed vector database for production AI applications. Fully managed, auto-scaling, with hybrid search (dense + sparse), metadata filtering, and namespaces. Low latency (<100ms p95). Use for production RAG, recommendation systems, or semantic search at scale. Best for serverless, managed infrastructure.