status

status is a command for coding agents from zilliztech/zilliz-plugin. It costs 27 tokens per session (471 once invoked), scanned A, original, Apache-2.0.

A command that reports the current Zilliz Cloud environment, including the selected context, cluster details, databases, collections, and collection statistics. Zilliz Cloud is a managed service for vector databases.

In plain words
What is it for?
Checking authentication and the active cluster, listing databases and collections, and reviewing collection statistics, indexes, and load status.
Why use it?
It gathers the main environment details in one check and identifies missing login or cluster context setup.

Command

Part of the zilliz plugin — 21 skills, 2 commands shipped together

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 commands/zilliztech/zilliz-plugin/status
Clone the repo
git clone --depth 1 https://github.com/zilliztech/zilliz-plugin

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.

agentmods badge for status

README.md
[![agentmods](https://agentmods.dev/badge/commands/zilliztech/zilliz-plugin/status.svg)](https://agentmods.dev/commands/zilliztech/zilliz-plugin/status)
Your own site
<a href="https://agentmods.dev/commands/zilliztech/zilliz-plugin/status"><img src="https://agentmods.dev/badge/commands/zilliztech/zilliz-plugin/status.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 471 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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00471
Opus 5 $0.00014 $0.00235
Sonnet 5 $0.00005 $0.00094
Haiku 4.5 $0.00003 $0.00047

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

Security

Grade A, and why

status 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/commands/status.md · 75 lines

What it actually says

Gather and display a status overview of the user's current Zilliz Cloud environment. Run commands with --output json for structured data, then present a formatted summary.

Step 1: Check Prerequisites

Verify CLI is installed and user is logged in:

zilliz auth status

If not set up, suggest running /zilliz:quickstart first.

Step 2: Show Current Context

zilliz context current --output json

If no context is set, suggest running zilliz context set --cluster-id <id>.

Step 3: Cluster Details

Using the cluster ID from context:

zilliz cluster describe --cluster-id <cluster-id> --output json

Present: cluster name, status, plan, region.

Step 4: Database List

zilliz database list --output json

Step 5: Collections Summary

For each database returned in Step 4, gather collection information:

zilliz collection list --database <db-name> --output json

For each collection, gather stats and index info:

zilliz collection get-stats --name <name> --database <db-name> --output json
zilliz collection get-load-state --name <name> --database <db-name> --output json
zilliz index list --collection <name> --database <db-name> --output json

Step 6: Present Summary

Format the results as a readable summary:

Cluster: () Status: RUNNING | Region: | Plan:

For each database, show its collections:

Database:

Collection Rows Load State Indexes
my_collection 10,000 Loaded vector_idx (AUTOINDEX)
... ... ... ...

If the cluster is suspended, show a warning that data operations are unavailable.

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.

  1. 4d ago First seen · 75 lines · 27 tokens per session scan A b3abe2b0e337

Subscribe to this mod's changes

status is a command published in the GitHub repository zilliztech/zilliz-plugin (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 27 tokens to every session and 471 once invoked, about $0.0001 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.