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 commands/weaviate/agent-skills/datagit clone --depth 1 https://github.com/weaviate/agent-skillsWhat 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.00003 | $0.00362 |
| Opus 5 | $0.00002 | $0.00181 |
| Sonnet 5 | $0.00001 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
data 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 2d 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
Create Example Data
Create example data in a specific domain and upload to a Weaviate collection.
Usage
/weaviate:data
/weaviate:data domain "finance" nrows 100
/weaviate:data domain "ecommerce" vectorizer "text2vec-weaviate"
Workflow
- Run the create example data script:
uv run ${CLAUDE_PLUGIN_ROOT}/skills/weaviate/scripts/example_data.py - Confirm the collection exists
uv run ${CLAUDE_PLUGIN_ROOT}/skills/weaviate/scripts/get_collection.py --name "COLLECTION_NAME"
Domain Datasets:
academiccontains a selection of chunked papers from Arxiv on the topic of AI/ML. Creates theAI_Arxivcollectionfinancecreates a fully synthetic dataset of Indian Income Tax Return forms. Creates theIncome_Tax_Returnscollectionecommercecontains structured e-commerce product information including product details, pricing, categorization. Creates theProduct_Catalogcollectionmedicalcontains information about common hair related diseases. Creates theHair_Medicalcollectioncustomer_supportcontains customer support tickets from IT. Creates theIT_Support_Ticketscollection
No other domains are supported.
Environment
Requires:
WEAVIATE_URL: Weaviate Cloud cluster URLWEAVIATE_API_KEY: API key for authentication
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.
- 2d ago First seen · 44 lines · 3 tokens per session scan A 824962e9ee93
data is a command published in the GitHub repository weaviate/agent-skills (103 stars, last pushed 2mo ago), licensed BSD-3-Clause. It adds 3 tokens to every session and 362 once invoked, about $0.0000 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 commands, from other repositories
merge
Finalize work on a branch: verify docs + tree are clean, merge to main, clean up. Supports both standard git checkout -b branches and git worktree flows — auto-detected at pre-flight.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
dev
Runs Vendure in development mode. By default it starts three processes: the GraphQL server (ts-node ./src/index.ts), the worker (ts-node ./src/index-worker.ts), and the dashboard (a Vite dev server).
start
Runs a project that has already been compiled with vendure build.
pipeline-undo
Undo a pipeline run's result. With worktree isolation (the current engine), this is clean and low-risk: a run never touches your checkout — its result lives only on a pipeline/ branch (and, for a --push run, on the remote). "Undo" therefore means deleting that branch and its worktree, not reverting your working tree.