cortex-remember

A tool for saving important decisions, discoveries, bug fixes, patterns, and other useful context in persistent memory for later sessions.

In plain words
What is it for?
Use it when you explicitly want something remembered, such as an architecture choice, a resolved bug, a coding pattern, or a lesson.
Why use it?
It reduces the need to explain the same project knowledge again and helps preserve information that remains useful beyond the current conversation.

Skill for Claude CodeCodex

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.

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

Made for: Claude Code, Codex.

Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 821 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00095 $0.00821
Opus 5 $0.00048 $0.00411
Sonnet 5 $0.00019 $0.00164
Haiku 4.5 $0.00010 $0.00082

Measured 2d ago against content hash c5042997b463, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cortex-remember 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 2d 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-remember/SKILL.md · 76 lines

How it starts

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

Remember — Store to Persistent Memory

Keywords

remember, save, store, note, bookmark, don't forget, important, keep this, record, persist, write down, save for later, remember this decision, store this pattern, note this lesson, save this fix

Overview

Store important information into Cortex's thermodynamic memory system. Memories pass through a predictive coding gate that automatically filters noise — only genuinely novel or important content gets stored. The system handles deduplication, entity extraction, and knowledge graph linking automatically.

Use this skill when: A significant event happens during a session — a decision is made, a bug is fixed, a pattern is discovered, or the user explicitly asks to remember something.

Workflow

Step 1: Identify What to Remember

Determine the content worth storing. Good candidates:

  • Decisions: "We chose PostgreSQL over SQLite because..."
  • Bug fixes: "The root cause was X, fixed by Y"
  • Patterns: "This codebase uses factory injection for all handlers"
  • Lessons: "Never use asyncio.get_event_loop() in Python 3.10+"
  • Context: "The user prefers minimal PRs with focused changes"

Step 2: Store the Memory

Call cortex:remember with structured content:

cortex:remember({
  "content": "<clear, self-contained description of what to remember>",
  "tags": ["<category>", "<project>", "<topic>"],
  "directory": "<current working directory>",
  "source": "<context: e.g. 'bug-fix', 'architecture-decision', 'user-preference'>"
})

Content guidelines:

  • Write content that will make sense in 3 months without context
  • Include the why, not just the what
  • Keep it under 2000 characters
  • Be specific: "PostgreSQL 15+ required for pgvector HNSW indexes" not "we use Postgres"

Step 3: Verify Storage

The response includes:

  • stored: true/false — whether the gate accepted it (false means too similar to existing memory)
  • memory_id — the stored memory's ID
  • novelty_score — how novel the content was vs existing memories
  • merged_with — if it was merged into an existing memory instead of creating new

Read the full file on GitHub · 76 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. 2d ago First seen · 76 lines · 95 tokens per session scan A c5042997b463

Subscribe to this mod's changes

cortex-remember is a skill published in the GitHub repository cdeust/Cortex (71 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 821 once invoked, about $0.0005 per session on Opus 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

promote-memory

Review candidate learnings in Claude Code's native auto memory (/.claude/projects/ /memory/, machine-local) and run them through a five-critic council in parallel: generality, staleness, redundancy, evidence, format. Majority vote (3+ of 5) promotes the entry to MEMORY.md. Use when user says "promote memory", "review…

pedrohcgs/claude-code-my-workflow · 106 tokens

checkpoint

Save a structured state snapshot before stopping or handing off. Captures the active plan, recent decisions, file pointers (with line numbers), open questions, and the next 1–3 actions into a checkpoint file under qualityreports/checkpoints/. Optionally proposes [LEARN] entries to add to MEMORY.md. Use when user says…

pedrohcgs/claude-code-my-workflow · 124 tokens

respond-to-eval

Turn student course evaluations (free-text + numeric) into an actionable teaching-improvement plan — the teaching analogue of /respond-to-referees. Clusters comments into themes, separates signal from noise, classifies each theme Keep / Change / Investigate / Out-of-scope, and drafts concrete changes mapped to the…

pedrohcgs/claude-code-my-workflow · 111 tokens

devils-advocate

Adversarial 5-7 question challenge to a deck's pedagogical choices — ordering, prerequisites, cognitive load, motivation. Use when user says "devil's advocate", "poke holes in this deck", "push back on my slides", "stress-test the design", "what would a skeptical student ask?". Read-only; surfaces questions to force…

pedrohcgs/claude-code-my-workflow · 89 tokens

pedagogy-review

Holistic pedagogical review of a lecture deck (.qmd or .tex). Checks narrative arc, prerequisite assumptions, worked examples, notation clarity, and deck-level pacing. Use when user says "pedagogy review", "does this teach well?", "is the flow right?", "will students follow?", "review the narrative", or before…

pedrohcgs/claude-code-my-workflow · 90 tokens

learn

Extract reusable knowledge from the current session into a persistent skill. Use when you discover something non-obvious, create a workaround, or develop a multi-step workflow that future sessions would benefit from.

pedrohcgs/claude-code-my-workflow · 41 tokens