automem
01Skill Claude Code
Persistent AutoMem memory via the legacy curl-based AutoMem skill.
41 tagged qdrant, measured the same way as everything else here.
Browse within: agent 27vector-database 27deployment 26scaling 26Orchestration 12a2a-protocol 11agent-orchestration 11langgraph 11embeddings 7hnsw 7similarity-search 7Production 6distributed 6semantic-search 6
Skill Claude Code
Persistent AutoMem memory via the legacy curl-based AutoMem skill.
redhat-community-ai-tools/UnifAI
Skill Claude CodeCursor
MAS domain knowledge — architecture, component routing, rules, recipes. Use when working on any file under multi-agent/.
Skill Claude CodeCodex
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…
phenomenoner/hermes-agent-harness-plus
Skill Claude CodeCodex
Use for compaction, coordination, or two complexity cues.
SkiTemplar/ultron-control-center
Skill Claude Code
Master orchestrator for the ULTRON system. Routes requests across memory layers, skill packs, hooks, and the AI Router (primary→fallback chain). Loads on every Ultron session via the SessionStart hook. Customize this file for your own workflows — the shipped version is a minimal starting template.
Skill Claude CodeCodex
Expert guide for building applications with Qdrant Edge — the embedded, offline-capable vector search engine for edge devices (robots, kiosks, mobile phones, IoT, home assistants). Use this skill whenever the user mentions Qdrant Edge, qdrant-edge-py, EdgeShard, on-device vector search, offline vector search, embedded…
Skill Claude CodeCodex
A personal memory system that stores text, images, files, and secrets in separate collections. It can find stored items by meaning rather than only by exact words.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: