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.
npx agentmods add skills/memorynexus/memory-nexus-plugins/memory-nexusnpx skills add MemoryNexus/memory-nexus-plugins --skill memory-nexusgit clone --depth 1 https://github.com/MemoryNexus/memory-nexus-pluginsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00445 |
| Opus 5 | $0.00000 | $0.00222 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
memory-nexus 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.
What it actually says
Memory Nexus
Store context, retrieve briefings, and maintain continuity across sessions with Memory Nexus.
Commands
/memory-nexus status
Check your Memory Nexus account status, including active tier and remaining quota.
/memory-nexus status
/memory-nexus search [query]
Search your stored memories by semantic meaning.
/memory-nexus search "how to set up authentication"
/memory-nexus forget [id]
Delete a stored memory by ID.
/memory-nexus forget memory-12345
/memory-nexus briefing
Get a structured briefing including directives, objectives, and contextual knowledge for your current project.
/memory-nexus briefing
/memory-nexus account
Manage your account, view tier, and billing information.
/memory-nexus account
How It Works
When you start a new Claude Code session:
- Automatic Detection: The plugin detects your git project and generates a unique hash
- Session Start: Memory Nexus retrieves your project's knowledge and context
- Briefing Injection: Structured directives, objectives, and knowledge are injected as context
- Seamless Continuity: Switch between Claude, Codex, or any other platform using the same API key
Pricing
| Tier | Cost | Monthly Quota |
|---|---|---|
| Solo | $7/month | 50 memories, 10 briefings |
| Crew | $49/month | 500 memories, 100 briefings |
| Fleet | $199/month | 5000 memories, 1000 briefings |
No free tier. No free trial.
Getting Started
- Create an account at memory-nexus.org
- Generate an API key from your account dashboard
- Set
MEMORY_NEXUS_API_KEYenvironment variable - Optionally set
MEMORY_NEXUS_API_BASE(defaults tohttps://api.memory-nexus.org) - Start a new Claude Code session — Memory Nexus will automatically load your project context
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 · 67 lines · 0 tokens per session scan A 5949607e1dbb
memory-nexus is a skill published in the GitHub repository MemoryNexus/memory-nexus-plugins (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 445 tokens. 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…