Query local Codex session history with jq. Use when users explicitly ask to search Codex sessions, inspect prior Codex conversations, find previous user messages, locate tool calls, summarize past work by working directory, or query Codex rollout JSONL files.
Automatically scan the current conversation, extract all "aha moments" and insights the user gained, and save them to a personal knowledge base. Use when the user says /aha, asks to capture learnings, or says /aha retag to consolidate and unify categories and tags across all saved insights.
A shared team memory skill backed by ChromaDB, a system for storing and searching text knowledge. It responds to requests about team knowledge, decisions, and shared memory.
Read-only gap analysis comparing an Obsidian vault's current quality setup against the 7-dimension methodology. Use when user says "audit vault", "check vault quality", "what's missing", "vault gaps", or wants to see how their vault measures up before running setup.
Persistent dual-layer memory engine with Notebook facts, curated RAG knowledge base, agent-driven knowledge graph, and general MCP helpers. Trigger proactively whenever user preferences, project conventions, technology stack choices, or architecture decisions are introduced, or when querying ingested documentation…
Search through Claude Code local chat history JSONL files to find information from past conversations. Use when the user asks "did we discuss X before", "what did we decide about Y", "how did we solve Z", or when context from a previous session would be useful. Searches all local session files efficiently via grep +…
Use when the user asks to check global knowledge, global directory, Obsidian memory, project history, company context, people notes, decisions, tasks, open loops, or anything that should be searched in the configured Obsidian vault.
A shared team memory skill using ChromaDB, a database for storing and searching information. It is intended for team knowledge, decisions, and shared memories.
Run health diagnostics on the amem memory database. Use when the user wants to check memory health, embedding coverage, stale memories, or diagnose issues.
Search and read the user's self-hosted Obsidian vault through the bundled OAuth MCP bridge. Use when the user asks about notes, vault search, or recent documents.
Use when substantive project work, structural code questions, research, planning, debugging, architecture, decisions, document ingest, incident recovery, or verified context and results should survive future sessions; also when the user invokes $using-lwc or asks to search, update, repair, configure, or maintain an…
Event Pod gives your agent a persistent world model — structured context that survives across sessions, models, and tools. Not a transcript. A causal model with certainty scores that gets sharper over time.
Drive the mcp-memory-graph MCP server like an expert: store, recall, and reconcile durable knowledge across sessions over 51 local tools ($0/token, one SQLite file). Use when ANY memory tool is in play (mcpmemory), when the user says "remember this" / "recall that" / "store a decision", when a memory seems missing…
Local-first agent memory MCP. No API keys. Prefer MCP tools if connected; otherwise the package CLI. Use when the user wants Delx Memory data or actions through an agent.
Build or update privacy-first AI-assistant configuration and reusable preference skills for Codex, Claude Code, Cursor, Gemini CLI, and similar tools. Use when the user provides explicit preferences, existing config files, example rules, or asks to optimize AGENTS.md, CLAUDE.md, assistant rules, memory files, or…
Bootstrap an agent collaboration system into an Obsidian vault — memory, protocols, task boards, and per-client instruction files via a conversational interview. Use when asked to "set up my vault", "onboard me", "bootstrap agent collaboration", "set up session protocols", "configure my vault for AI", or at the start…
Give the agent durable, local memory with engram — recall past decisions before answering, and persist new decisions, preferences and facts as they happen. Use when work spans sessions or the user says "remember".
Analyze and improve a note for slipbox integration using the actual slipbox via MCP tools. Use when the user shares a note and asks to analyze it, improve it, integrate it, check atomicity, find connections, suggest tags, or refine it. Trigger on: analyze this note, check this zettel, is this atomic, what should this…
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.
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: