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/backupnpx skills add zilliztech/zilliz-plugin --skill backupgit 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/backup)<a href="https://agentmods.dev/skills/zilliztech/zilliz-plugin/backup"><img src="https://agentmods.dev/badge/skills/zilliztech/zilliz-plugin/backup.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.00032 | $0.00833 |
| Opus 5 | $0.00016 | $0.00417 |
| Sonnet 5 | $0.00006 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
backup 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 yesterday.
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 — 113 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).
- No cluster context required -- backup operations use
--cluster-iddirectly.
Commands Reference
Create a Backup
zilliz backup create --cluster-id <cluster-id>
# Optional:
# --database <database-name>
# --collection <collection-name>
# --backup-type <CLUSTER|COLLECTION>
# Or use raw JSON: --body '{...}'
List Backups
zilliz backup list
# Optional:
# --project-id <filter-by-project-id>
# --cluster-id <filter-by-cluster-id>
# --creation-method <MANUAL|AUTO>
# --backup-type <CLUSTER|COLLECTION>
# Pagination: --page-size <n> --page <n>
# Fetch all pages: --all
Describe a Backup
zilliz backup describe --cluster-id <cluster-id> --backup-id <backup-id>
Delete a Backup
zilliz backup delete --cluster-id <cluster-id> --backup-id <backup-id-to-delete>
Export a Backup
zilliz backup export \
--cluster-id <cluster-id> \
--backup-id <backup-id> \
--integration-id <storage-integration-id>
# Optional: --directory <directory>
Restore to a New Cluster
zilliz backup restore-cluster \
--cluster-id <source-cluster-id> \
--backup-id <backup-id-to-restore> \
--project-id <target-project-id> \
--name <new-cluster-name> \
--cu-size <compute-units-for-new-cluster> \
--collection-status <KEEP|RELEASE>
# Optional: --restore-version-policy <LATEST|ORIGINAL>
Restore Specific Collections
zilliz backup restore-collection \
--cluster-id <source-cluster-id> \
--backup-id <backup-id> \
--dest-cluster-id <destination-cluster-id>
# Or use raw JSON: --body '{"collections": [{"source": "col1", "target": "col1_restored"}]}'
Describe Backup Policy
zilliz backup describe-policy --cluster-id <cluster-id>
Update Backup Policy
zilliz backup update-policy --cluster-id <cluster-id> --auto-backup <true|false>
# Optional:
# --frequency <frequency>
# --start-time <start-time>
# --retention-days <days-to-retain-backups>
# Or use raw JSON: --body '{...}'
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.
- yesterday Changed · +1 lines f9a4003a9dd4
- 5d ago First seen · 112 lines · 32 tokens per session scan A f5028072ffad
backup is a skill published in the GitHub repository zilliztech/zilliz-plugin (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 833 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.
debugging
How to debug tursodb using Bytecode comparison, logging, ThreadSanitizer, deterministic simulation, and corruption analysis tools.
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…