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/sunil-goyal-1502/project-memory/memory-extractnpx skills add sunil-goyal-1502/project-memory --skill memory-extractgit clone --depth 1 https://github.com/sunil-goyal-1502/project-memoryWrote 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.
[](https://agentmods.dev/skills/sunil-goyal-1502/project-memory/memory-extract)<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>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.
| Model | Per session | Once 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 |
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.
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
-
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."
-
Read the condensed transcript from
.ai-memory/.last-session.txt. -
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"} -
Append extracted decisions to
.ai-memory/decisions.jsonl(one JSON line per decision). -
Delete
.ai-memory/.last-session.txt(it has been processed). -
Run sync to update tool-specific files:
node -e "require('${CLAUDE_PLUGIN_ROOT}/scripts/sync-tools.js').syncAll(process.cwd())" -
Report results: Show how many decisions were extracted, grouped by category.
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.
- 4d ago First seen · 53 lines · 7 tokens per session scan A 78726ec62ef6
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.
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.
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.…
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…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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.
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…