memory-extract

memory-extract is a skill for Claude Code, Codex from sunil-goyal-1502/project-memory. It costs 7 tokens per session (602 once invoked), scanned A, original, MIT.

A tool for extracting project decisions from the saved transcript of the previous coding session.

In plain words
What is it for?
Recovering decisions about scope, technical conventions, constraints, and unresolved choices when starting a new session.
Why use it?
It separates lasting choices and constraints from routine implementation notes, questions, and tool updates.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the project-memory plugin — 11 skills, 2 agents, 1 MCP server shipped together

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/sunil-goyal-1502/project-memory/memory-extract
Any agent
npx skills add sunil-goyal-1502/project-memory --skill memory-extract
Clone the repo
git clone --depth 1 https://github.com/sunil-goyal-1502/project-memory

Made for: Claude Code, Codex.

Or install project-memory, the plugin that ships this one along with the rest of its 11 skills, 2 agents, 1 MCP server.

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 memory-extract

README.md
[![agentmods](https://agentmods.dev/badge/skills/sunil-goyal-1502/project-memory/memory-extract.svg)](https://agentmods.dev/skills/sunil-goyal-1502/project-memory/memory-extract)
Your own site
<a href="https://agentmods.dev/skills/sunil-goyal-1502/project-memory/memory-extract"><img src="https://agentmods.dev/badge/skills/sunil-goyal-1502/project-memory/memory-extract.svg" alt="Measured on agentmods" height="20"></a>
Per session 7 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 602 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.00007 $0.00602
Opus 5 $0.00003 $0.00301
Sonnet 5 $0.00001 $0.00120
Haiku 4.5 $0.00001 $0.00060

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

Security

Grade A, and why

memory-extract 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 4d 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/memory-extract/SKILL.md · 53 lines

How it starts

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

Extract Decisions from Previous Session

Analyze the condensed transcript from the previous session and extract project decisions.

Steps

  1. Check for pending transcript: Read .ai-memory/.last-session.txt.

    • If it doesn't exist or is empty, tell the user: "No previous session transcript found. Decisions are captured automatically when a session ends and extracted at next session start."
  2. Read the condensed transcript from .ai-memory/.last-session.txt.

  3. Perform the extraction yourself using these rules:

    INCLUDE (these ARE decisions):

    • Why-decisions: "We chose X because Y", "Let's use X for Y"
    • Constraints: "We can't use X because Y", "X must be Y"
    • Scope: "Let's not do X for now", "X is out of scope"
    • Conventions: "Let's name X as Y", "We'll follow X pattern"
    • Unresolved: "We need to figure out X", "TODO: decide on X"

    EXCLUDE (these are NOT decisions):

    • Implementation details (specific code changes, debugging steps)
    • Git operations and file management
    • Questions that were fully resolved in the same session
    • Tool usage and progress updates

    DEDUPLICATION:

    • If the same decision appears multiple times, keep only the most refined version
    • If a decision was made and then changed, keep only the final version

    OUTPUT FORMAT: For each decision, produce a JSON line:

    {"id":"<8-hex>","ts":"<ISO8601>","category":"architecture|constraint|convention|testing|scope|unresolved","decision":"<one sentence>","rationale":"<why>","confidence":<0.0-1.0>,"source":"auto"}
    
  4. Append extracted decisions to .ai-memory/decisions.jsonl (one JSON line per decision).

  5. Delete .ai-memory/.last-session.txt (it has been processed).

  6. Run sync to update tool-specific files:

    node -e "require('${CLAUDE_PLUGIN_ROOT}/scripts/sync-tools.js').syncAll(process.cwd())"
    
  7. Report results: Show how many decisions were extracted, grouped by category.

Read the full file on GitHub · 53 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. 4d ago First seen · 53 lines · 7 tokens per session scan A 78726ec62ef6

Subscribe to this mod's changes

memory-extract is a skill published in the GitHub repository sunil-goyal-1502/project-memory (8 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 602 once invoked, about $0.0000 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-31.

Related

Other skills, from other repositories

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

agent-memory

../../../engineering/agent-memory/skills/agent-memory/SKILL.md.

alirezarezvani/claude-skills · 0 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens