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.
git 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/commands/zilliztech/zilliz-plugin/quickstart)<a href="https://agentmods.dev/commands/zilliztech/zilliz-plugin/quickstart"><img src="https://agentmods.dev/badge/commands/zilliztech/zilliz-plugin/quickstart/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/commands/zilliztech/zilliz-plugin/quickstart"><img src="https://agentmods.dev/badge/commands/zilliztech/zilliz-plugin/quickstart.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.00024 | $0.00484 |
| Opus 5.5 | $0.00010 | $0.00194 |
| Sonnet 5.5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade C, and why
quickstart scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/zilliztech/zilliz-cli/master/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/zilliztech/zilliz-cli/master/install.sh | bash What it actually says
Guide the user through the complete Zilliz Cloud CLI setup. Follow these steps in order:
Step 1: Install zilliz-cli
Check if already installed:
zilliz --version
If not installed or needs upgrading:
curl -fsSL https://raw.githubusercontent.com/zilliztech/zilliz-cli/master/install.sh | bash
Verify:
zilliz --version
Step 2: Authenticate
Check if already logged in:
zilliz auth status
If not logged in, instruct the user to open their own terminal and run one of:
- Browser login (recommended) —
zilliz login— opens browser for OAuth, full feature access. - API Key via login —
zilliz login --api-key— prompts for API key, no browser needed. - API Key via configure (legacy) —
zilliz configure— prompts for API key, simpler setup. - Environment variable — add
export ZILLIZ_API_KEY=<key>to.zshrc/.bashrc.
IMPORTANT: These commands require interactive input and cannot run inside Claude Code. Do NOT ask the user to paste API keys into the chat.
Wait for the user to confirm login is complete, then verify:
zilliz auth status
Step 3: Select a Cluster
List available clusters:
zilliz cluster list
If no clusters exist, offer to create one:
zilliz project list
zilliz cluster regions
zilliz cluster create --type serverless --name <name> --project-id <id> --region <region>
Step 4: Set Cluster Context
Set the active cluster for data operations:
zilliz context set --cluster-id <selected-cluster-id>
Step 5: Verify
Confirm everything works:
zilliz context current
zilliz collection list
Report the setup result to the user, showing their cluster ID, endpoint, and database.
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 · 85 lines · 24 tokens per session scan C ddfab5b4a116
quickstart is a command published in the GitHub repository zilliztech/zilliz-plugin (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 484 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
boss:ship
A command that builds, deploys, and health-checks a project that has already passed testing, then records the release details in a deployment report.
cloudflare-images:validate-config
Validate wrangler.jsonc configuration, verify Cloudflare Images bindings, check environment variables, and test Workers integration. Ensures correct setup for using Cloudflare Images with Cloudflare Workers.
cloudflare-queues:setup
Interactive wizard to set up Cloudflare Queues with queue creation, producer/consumer binding configuration, and Dead Letter Queue setup. Use when user wants to create first queue or add queues to existing Worker.
cloudflare-workers:migrate
Platform migration assistant for moving applications from AWS Lambda, Vercel, Netlify, or Cloudflare Pages to Cloudflare Workers.
cloudflare-images:check
Run comprehensive health check and configuration validation for Cloudflare Images. Tests API connectivity, verifies authentication, checks transformations enabled, lists variants, and shows quota usage.
cloudflare-queues:troubleshoot
Quick troubleshooting for common Cloudflare Queues issues.