cortex-explore-memory

cortex-explore-memory is a skill for Claude Code from cdeust/Cortex. It costs 91 tokens per session (683 once invoked), scanned A, original, MIT.

A skill for examining the state of Cortex, a system that stores an AI assistant's memories and knowledge. It reports stored memories, topic coverage, relationships, and knowledge gaps.

In plain words
What is it for?
Use it to check memory health, assess coverage of a project or topic, find missing knowledge, and diagnose sparse areas.
Why use it?
It helps show what the memory system knows, where information is weak, and whether stored knowledge is becoming outdated.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the hypermnesia-mcp plugin — 13 skills, 3 commands, 2 MCP servers shipped together

Good fit Use it to check memory health, assess coverage of a project or topic, find missing knowledge, and diagnose sparse areas.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cdeust/cortex/cortex-explore-memory
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.

Any agent
npx skills add cdeust/Cortex --skill cortex-explore-memory
Clone the repo
git clone --depth 1 https://github.com/cdeust/Cortex

Made for: Claude Code.

Or install hypermnesia-mcp, the plugin that ships this one along with the rest of its 13 skills, 3 commands, 2 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for cortex-explore-memory

README.md
[![agentmods](https://agentmods.dev/badge/skills/cdeust/cortex/cortex-explore-memory/github.svg)](https://agentmods.dev/skills/cdeust/cortex/cortex-explore-memory)
Your own site
<a href="https://agentmods.dev/skills/cdeust/cortex/cortex-explore-memory"><img src="https://agentmods.dev/badge/skills/cdeust/cortex/cortex-explore-memory/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for cortex-explore-memory

Your own site · 80×15
<a href="https://agentmods.dev/skills/cdeust/cortex/cortex-explore-memory"><img src="https://agentmods.dev/badge/skills/cdeust/cortex/cortex-explore-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 683 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00091 $0.00683
Opus 5.5 $0.00036 $0.00273
Sonnet 5.5 $0.00018 $0.00137
Haiku 4.5 $0.00009 $0.00068

Measured 1mo ago against content hash a03a2d050ab9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cortex-explore-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 1mo ago.

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.

skills/cortex-explore-memory/SKILL.md · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Explore Memory — Diagnostics, Gaps, and Coverage

Keywords

memory stats, diagnostics, coverage, gaps, what am I missing, memory health, knowledge gaps, weak areas, isolated entities, sparse domains, how much do I know, memory overview, system status, knowledge assessment

Overview

Understand the state of your memory system — what's stored, what's missing, what's decaying, and where knowledge is strong or weak. This skill combines multiple diagnostic tools to give you a complete picture.

Use this skill when: Starting a new project phase, after a long break, or when you want to understand what Cortex knows and doesn't know about a topic.

Workflow

Step 1: Quick Health Check

Get system-level diagnostics:

cortex:memory_stats({})

Returns: total memories, heat distribution, store type breakdown (episodic vs semantic), entity count, relationship count, average confidence, and decay statistics.

Step 2: Assess Knowledge Coverage

Score how well a topic or project is covered:

cortex:assess_coverage({
  "domain": "<project or topic>",
  "query": "<specific area to assess>"
})

Returns a 0-100 coverage score with specific recommendations on what to document or remember next.

Step 3: Detect Knowledge Gaps

Find isolated entities, sparse domains, and temporal drift:

cortex:detect_gaps({
  "domain": "<optional domain filter>"
})

Returns:

  • Isolated entities — entities mentioned but not connected to memories
  • Sparse domains — project areas with few memories
  • Temporal gaps — periods with no memory activity (potential knowledge loss)
  • Orphan clusters — groups of memories disconnected from the main knowledge graph

Step 4: Validate Against Filesystem

Check if memories reference files/paths that still exist:

cortex:validate_memory({
  "directory": "<project root>"
})

Flags stale memories that reference deleted files, moved modules, or renamed functions — keeping the knowledge base accurate.

Read the full file on GitHub · 95 lines

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.

  1. 1mo ago First seen · 95 lines · 91 tokens per session scan A a03a2d050ab9

Subscribe to this mod's changes

cortex-explore-memory is a skill published in the GitHub repository cdeust/Cortex (75 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 683 once invoked, about $0.0004 per session on Opus 5.5. 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-30.

Related

Other skills, from other repositories

xmemo-memory

Persistent, user-owned memory for agents. Use the standalone runtime to remember, recall, search, preserve restart continuity, manage TODOs and expenses, inspect account overview, activity and stats diagnostics, or diagnose XMemo when MCP tools are unavailable. Not for codebase search, web search, or short-lived…

yonro/memory-os-cli · 68 tokens

knowledge-audit

Review and clean up stored memories — find duplicates, contradictions, stale entries, and consolidate.

n24q02m/mnemo-mcp · 21 tokens

temporal-query

Answer time-travel questions over stored memory — what was believed at a past point in time, when a belief changed, and what replaced it. Use when the user says "as of", "back in", "at the time", "history of", "timeline", "what did I think then", or asks why a current memory contradicts an older one.

n24q02m/mnemo-mcp · 77 tokens

memory-commit

Use when the user explicitly says "remember this", "save this", "ghi nho", "luu lai", "save for next time", or otherwise asks to persist the immediately preceding context. Captures with the appropriate contexttype (decision, preference, fact, skill, task, conversation) so future sessions can retrieve it accurately.

n24q02m/mnemo-mcp · 72 tokens

recall-context

Use at session start, before significant decisions, or when a new task references a known project to recall mnemo memories matching the current working directory, recently edited files, or topic keywords. Helps maintain continuity across sessions and avoid redoing past research.

n24q02m/mnemo-mcp · 53 tokens

passport-bootstrap

Use when the user installs mnemo-mcp on a fresh machine and wants to restore prior memory state from S3 or Google Drive (Phase 2 passport sync). Triggers on phrases like "set up mnemo on this machine", "restore my memory passport", "import passport", "bootstrap mnemo", or when the user says they got a new laptop / VM…

n24q02m/mnemo-mcp · 83 tokens