12,529 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
System Skill reference implementation showing how to build Claude Skills with persistent memory. Demonstrates the CLI + SKILL.md + Database pattern for creating tools that learn and improve over time.
★not rated 56 1y agoA
tokens not measured
originalMIT
MCP server "ai-memory" as configured in alphaonedev/ai-memory-mcp. Runs in Docker (ghcr.io/alphaonedev/ai-memory:0.5.1). Needs 1 environment variable to run.
★not rated 56 yesterdayA
tokens not measured
originalApache-2.0
Persistent, private, local-first memory for Claude Code. Your agent remembers your code and decisions across sessions — one static binary, no cloud, nothing leaves your machine.
★not rated 56▲
+2 3mo agoA
tokens not measured
originalMIT
Persistent Obsidian-based memory for coding agents. Automatically orients from a knowledge vault at session start, navigates project architecture via graph traversal, and writes discoveries back to the vault.
★not rated 55 7mo agoA
tokens not measured
originalMIT
Operator procedure to declare and provision a new Knowledge Base GitOps-style, so it survives pod restarts; also covers authoring the KB's artifacts (skills, subagents, hooks, MCP descriptors) and the SOPS encryption flow.
Turn a Claude Cowork project into a company brain your team owns: guided setup, a Memory Update protocol, a knowledge-transfer interview, a senior strategy skill, a decision lifecycle with daily signal sweeps and a weekly Decision Radar, a sales/pipeline follow-up layer, a LinkedIn editor, mission mode, and recurring…
★not rated 53▲
+3 8d agoA
tokens not measured
originalMIT
Manually trim, compact, persist, and repair Claude Code conversation sessions stored as JSONL files. Use when the user wants to: (1) fix a session hitting 'Prompt is too long' errors, (2) manually compact or strip a session to reduce context, (3) analyze a session's token usage and message chain, (4) strip tool call…
Compound engineering with persistent memory and multi-agent workflows based on beads. 30 specialized agents, 28 commands, 15 skills, and automatic knowledge capture/recall.
★not rated 53▲
+1 15d agoA
tokens not measured
originalMIT
Personal knowledge management for Obsidian combining GTD, Zettelkasten, and PARA. Six workflows: (1) Capture - "capture this", "remember this", "save this thought", "note this down" - saves thoughts/tasks to daily inbox without categorization; (2) Process inbox - "process my inbox", "organize captures", "GTD…
Record an orchestrated run (epic/auto/chain implementation, ship, release preparation, hardening) into gyeol episodic memory. Invoke yourself as the final step whenever such a run completes, aborts, or is interrupted. Installed and managed by gyeol; modifies no other skill.
Interact with Obsidian using the official CLI to read, search, create, and manage notes, daily notes, tasks, properties, and more. Use when the user wants to query or manipulate vault content via the obsidian command.
Always use when working in Kimi Work desktop sessions that should read from or save to the user's Familiar second brain. Trigger for memory, notes, projects, prior work, research, summaries, durable outputs, "save this", "remember this", "from my brain", "what do I know", or any request that should use the local…
Persistent cognitive memory for AI agents — query, record, review, and consolidate knowledge across sessions with spreading activation, FSRS scheduling, and NLI contradiction detection.
Search, recover, inspect, export, and analyze local AI session history with AI Session Search (aise) across Claude Code, Claude Desktop local agent, Codex, Cursor, Antigravity, Pi coding agent, Prime Agent, Google AI Studio, and Gemini CLI. Use when asked to "find prior AI work", "recover context after compaction"…
Auto-improving AI sub-agents that learn from their mistakes across sessions.
★not rated 50 5d agoA
tokens not measured
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: