What is nexus-memory?

A plugin that stores and retrieves project memories using Qdrant, a database designed for searching related information. It is intended for Claude Code and can run on your own system.

It supports automatic recall of stored memories before a prompt and automatic capture of new facts after a turn.

It helps an agent remember relevant facts between conversations instead of starting with no previous context each time.

nexus-memory — Plugin by Neboy72

Install

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.

Claude Code

/plugin marketplace add Neboy72/nexus-memory

agentmods

npx agentmods add plugins/neboy72/nexus-memory/claude-code

Clone the repo

git clone --depth 1 https://github.com/Neboy72/nexus-memory

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

nexus-memory 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 yesterday.

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.

plugins/claude-code/.claude-plugin/plugin.json · 10 lines

What it actually says

{
  "name": "nexus-memory",
  "version": "0.8.0",
  "description": "Persistent memory for Claude Code via Qdrant. Auto-Recall injects relevant memories before each prompt. Auto-Capture stores facts after each turn. Self-hosted, private, universal.",
  "author": {
    "name": "Neboy72",
    "url": "https://github.com/Neboy72/nexus-memory"
  },
  "hooks": "./hooks/nexus-hooks.json"
}

Changes

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.

yesterday First seen · 10 lines scan A a3eb3b099871

Subscribe to this mod's changes

nexus-memory is a plugin published in the GitHub repository Neboy72/nexus-memory (2 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Data and AI Databases Memory and context ai ai-agents claude-code codex cursor knowledge-graph

engram

The context spine that 10x's your Claude Code sessions. Local-first SQLite knowledge graph + MCP server that intercepts file reads and replaces them with structural summaries. Measured 89% token reduction on a real codebase. Apache 2.0, no cloud, no telemetry.

NickCirv/engram · not measured

nexus-memory

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

engram

qualixar

engram-marketplace

superlocalmemory-codex

superlocalmemory

dhevenddra