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/zilliztech/zilliz-plugin/statusnpx skills add zilliztech/zilliz-plugin --skill statusgit 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/status)<a href="https://agentmods.dev/skills/zilliztech/zilliz-plugin/status"><img src="https://agentmods.dev/badge/skills/zilliztech/zilliz-plugin/status.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.00031 | $0.00470 |
| Opus 5 | $0.00015 | $0.00235 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
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 5d 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.
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, use the quickstart skill 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.
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.
- 5d ago First seen · 75 lines · 31 tokens per session scan A e3eeac67ec94
status is a skill published in the GitHub repository zilliztech/zilliz-plugin (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 470 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.
Other skills, from other repositories
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
volcengine-rds-postgresql
使用火山引擎 RDS PostgreSQL，帮助用户完成 RDS PostgreSQL 相关的实例管理、数据库操作、账号管理和运维任务，可直接调用 uv run ./scripts/callrdspostgresql.py 脚本获取实时结果。.