Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    memorius

    1

    A self-contained vector memory vault for AI agents to store, search, and recall context across sessions.

    Free

    Security scanned
    memorius

    memorius

    Example session with this skill installed

    I finally fixed that race condition in the token refresh logic. It was a missing mutex lock in auth.ts. Store this for me.

    • Read your context and instructions
    • Compiled the memorius

    Memory detected: Bug fix for token refresh race condition.
    Store this? (y/n)

    ✅ Stored: "Fix: race condition in token refresh logic. Root cause: missing mutex lock in auth.ts. Solution: added mutex lock."
    Shelf: bugs
    Folder: authentication
    Note: token-refresh-fix

    Next steps

    • Run memorius search "token refresh" to verify retrieval.
    • Use memorius diary at the end of the session to document the full implementation.
    • Consider running memorius consolidate if you have other notes on auth concurrency.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Agents lose context across sessions, leading to repetitive questions and lost insights. Memorius provides a persistent, self-contained memory vault that allows any AI agent to store, search, and recall information using vector embeddings and session diaries.

    What it does

    • Vector search finds relevant memories based on semantic meaning rather than just keyword matches.
    • Auto-capture triggers detect bug fixes, learning moments, decisions, and preferences to suggest storage.
    • Context injection retrieves past work and project details to inform current agent responses.
    • Session diaries generate summaries of accomplishments and decisions at the end of long work sessions.
    • Information mining extracts structured memories from meeting transcripts, documents, and PDF files.
    • Vault management includes tools for consolidating duplicates, checking facts, and organizing data into shelves and folders.

    How it works

    1. Store memories via CLI or agent hooks by providing content and optional shelf/folder metadata.
    2. Search the vault using natural language queries to retrieve the most relevant past entries with confidence scores.
    3. Inject context into the current session by running the context command to feed previous findings back into the agent prompt.
    4. Consolidate the vault periodically to merge similar entries and maintain a clean, high-signal memory set.

    Frameworks & tools

    Built as a standalone CLI tool and MCP server. It uses local vector embeddings (all-MiniLM-L6-v2) for privacy and supports integrations with Obsidian, Claude Desktop, and common developer shells.

    Why this beats prompting it yourself

    Generic system prompts for "remembering" rely on the finite context window of a single session. Memorius offloads this to a persistent local database, allowing for multi-week project recall that doesn't bloat your token usage.

    Use cases

    • Bug tracking to remember root causes and fixes for recurring architectural issues.
    • Developer preferences to persist coding styles, preferred libraries, and workflow patterns.
    • Meeting synthesis to extract action items and decisions from long chat transcripts or logs.
    • Project onboarding to quickly inject all previous context when starting a new task in an old repo.

    Known limitations

    Requires local storage access at ~/.memorius/data. Shell hooks require explicit user permission to modify shell configuration files. Large vaults (>100 memories) require periodic manual consolidation.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Requires local storage access. Shell hooks modify shell configs. Large vaults need periodic consolidation. No built-in encryption for stored memory files.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 22 days ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files
    Environment Variables

    Need to install memorius pypi package

    Listed22 days ago

    What's inside

    Frequently Asked Questions

    Memorius provides a persistent vector database that allows agents to 'remember' context across different sessions, preventing the loss of information once a chat window is closed or a context limit is reached. It solves the problem of agents repeating questions or forgetting project-specific decisions made days or weeks prior.

    Memorius is designed as a standalone CLI tool and an MCP (Model Context Protocol) server, making it compatible with Claude Desktop, IDE-integrated agents, and any developer shell. It works with any agent that can execute shell commands or interface with MCP servers.

    Unlike standard prompts that consume expensive token space in a single session, Memorius stores data locally in a searchable vault. This allows the agent to pull only the most relevant 'memories' into the prompt as needed, keeping token usage low while maintaining access to a massive history of work.

    Your purchase includes the Memorius CLI tool, the MCP server integration, and the local vector embedding engine. You also get the documentation for setting up auto-capture triggers and session diaries to automate your memory management.

    Setup involves installing the tool and granting it permission to create a local directory at `~/.memorius/data`. If you want to use shell hooks for automatic memory capture, you will need to give explicit permission for the tool to update your shell configuration files.

    Privacy is a core feature; Memorius uses the `all-MiniLM-L6-v2` model to generate vector embeddings locally on your machine. Your memories, project details, and session diaries are stored in your local file system and are never sent to a third-party cloud for storage or processing.

    New in Agents & Orchestration

    Free