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/ssube/conclave/chromadbnpx skills add ssube/conclave --skill chromadbgit clone --depth 1 https://github.com/ssube/conclaveWrote 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/ssube/conclave/chromadb)<a href="https://agentmods.dev/skills/ssube/conclave/chromadb"><img src="https://agentmods.dev/badge/skills/ssube/conclave/chromadb.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.00042 | $0.00972 |
| Opus 5 | $0.00021 | $0.00486 |
| Sonnet 5 | $0.00008 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
chromadb 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ChromaDB Skill
Semantic search and vector storage using ChromaDB for finding similar content across collections.
Requirements
pip install chromadb
Usage
Query for similar items
python3 {baseDir}/query.py query "gothic fantasy creature" --collection models [--limit 5]
Find similar to existing item
python3 {baseDir}/query.py similar <id> --collection models [--limit 5]
Add or update content (upsert)
python3 {baseDir}/query.py add --collection models --id <id> --text "..." [--metadata '{"key": "value"}']
This command performs an upsert: if the ID already exists, it updates the content; otherwise, it creates a new entry.
List collections
python3 {baseDir}/query.py collections
Create a new collection
python3 {baseDir}/query.py create-collection <name>
Delete an item
python3 {baseDir}/query.py delete <id> --collection models
Collections
Pre-defined collections for different use cases:
| Collection | Purpose |
|---|---|
models |
LoRA model descriptions (name, category, style notes) |
memories |
Bot memories and learned context |
notes |
User notes and reference material |
posts |
Posted content for semantic similarity checking |
Environment Variables
All variables are optional with sensible defaults:
CHROMADB_HOST: ChromaDB server hostname (default:localhost)CHROMADB_PORT: ChromaDB server port (default:8000)CHROMADB_PATH: Path for persistent storage (optional, uses server if not set)
Default Mode: The skill connects to the ChromaDB server at localhost:8000 by default. To use persistent local storage instead, set CHROMADB_PATH=/path/to/storage.
Metadata
Each item can have metadata for filtering:
python3 {baseDir}/query.py add \
--collection models \
--id creature_v2 \
--text "A LoRA for generating fantasy creatures with detailed scales and claws" \
--metadata '{"category": "creatures", "base_model": "flux", "quality": 5}'
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 140 lines · 42 tokens per session scan A 82322778f578
chromadb is a skill published in the GitHub repository ssube/conclave (2 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 972 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-31.
Other skills, from other repositories
vector-backend-operations
Select and connect the right vector-store backend for the vector-mcp MCP server — chromadb, postgres/pgvector, qdrant, couchbase, or mongodb — and supply the correct dbtype/connection parameters that every collection and search call needs. Use when the agent must decide which engine to target, wire up…
vector-collection-management
Create, populate, list, and delete vector-store collections through the vector-mcp MCP server's vectorcollectionmanagement tool. Use when the agent must stand up a new RAG collection, ingest documents (from a directory, file paths/URLs, or raw text) into an existing collection, enumerate collections, or drop one …
vector-mcp-operations
Operate vector-mcp through its governed MCP and GraphOS capabilities. Use for collection lifecycle, root-confined document ingestion, semantic or lexical retrieval, hybrid search, backend readiness, troubleshooting, and sanitized verification evidence.
vector-databases
Vector database operations — embed, store, search, and build RAG pipelines.
mysql reporter
生成 MySQL 查询报表并生成可视化图表。当用户需要查询 MySQL 数据库并以报表形式展示结果时使用此技能,包括:统计销售数据、分析用户行为、生成业务报表、查询业务指标等。.
qdrant-clients-sdk
Qdrant provides client SDKs for various programming languages, allowing easy integration with Qdrant deployments.