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/monitoringnpx skills add zilliztech/zilliz-plugin --skill monitoringgit 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/monitoring)<a href="https://agentmods.dev/skills/zilliztech/zilliz-plugin/monitoring"><img src="https://agentmods.dev/badge/skills/zilliztech/zilliz-plugin/monitoring.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.00665 |
| Opus 5 | $0.00015 | $0.00332 |
| Sonnet 5 | $0.00006 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
monitoring 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.
How it starts
The opening of the file, as written. The whole thing — 89 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).
- Cluster context set for collection-level monitoring (see setup skill).
Commands Reference
All monitoring commands that target collections accept an optional --database <db-name> flag. If omitted, the database from the current context is used.
Cluster Status
# Current context
zilliz context current
# Cluster details (status, plan, region, endpoints)
zilliz cluster describe --cluster-id <cluster-id>
Collection Overview
List all collections with their stats:
# List collections
zilliz collection list
zilliz collection list --database <db-name>
# For each collection, get stats and load state:
zilliz collection get-stats --name <collection-name>
zilliz collection get-load-state --name <collection-name>
If the cluster has multiple databases, iterate through each database by running zilliz database list first, then zilliz collection list --database <db-name> for each.
Database Overview
zilliz database list
All Clusters
zilliz cluster list --all
Time-series Metrics
For cluster-wide time series (CU sizing, storage, serverless VCU, slow queries) use zilliz cluster metrics:
zilliz cluster metrics --cluster-id <cluster-id> -m CU_COMPUTATION --period 1h
For per-collection time series (QPS, latency, entity counts, hybrid-search aliases) use zilliz collection metrics -- see the collection skill for metric scope rules and the full alias list:
zilliz collection metrics -c <collection-name> -m SEARCH_QPS --period 1h
Both commands render an inline Braille line chart by default (one block per metric with a min / max / avg / last summary). Pass an explicit -o table (or --output table) for the pivot-table layout, or use -o json / --query to get raw data for scripting.
Presenting Results
When the user asks for a status overview, collect and present information as a summary table:
Cluster Info:
- Cluster ID, name, status (RUNNING/SUSPENDED/etc.)
- Plan type, region, create time
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 · 89 lines · 31 tokens per session scan A 4c490426ea81
monitoring 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 665 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…