project-memory

project-memory is a skill for Claude Code, Codex from cobibean/shared-skills-registry-mcp. It costs 102 tokens per session (965 once invoked), scanned A, original, MIT.

A project memory workflow that records important work, decisions, discoveries, and unresolved questions in dated Markdown files so later coding-agent sessions can continue with context.

In plain words
What is it for?
Use it before substantial work to review recent notes and after meaningful work to save a concise record of what happened and what remains.
Why use it?
It reduces repeated investigation and prevents useful project knowledge from being lost between sessions or agents.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

Good fit Use it before substantial work to review recent notes and after meaningful work to save a concise record of what happened and what remains.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cobibean/shared-skills-registry-mcp/project-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 cobibean/shared-skills-registry-mcp --skill project-memory
Clone the repo
git clone --depth 1 https://github.com/cobibean/shared-skills-registry-mcp

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/cobibean/shared-skills-registry-mcp/project-memory/github.svg)](https://agentmods.dev/skills/cobibean/shared-skills-registry-mcp/project-memory)
Your own site
<a href="https://agentmods.dev/skills/cobibean/shared-skills-registry-mcp/project-memory"><img src="https://agentmods.dev/badge/skills/cobibean/shared-skills-registry-mcp/project-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 project-memory

Your own site · 80×15
<a href="https://agentmods.dev/skills/cobibean/shared-skills-registry-mcp/project-memory"><img src="https://agentmods.dev/badge/skills/cobibean/shared-skills-registry-mcp/project-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 965 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.
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.00102 $0.00965
Opus 5 $0.00051 $0.00483
Sonnet 5 $0.00020 $0.00193
Haiku 4.5 $0.00010 $0.00097

Measured 10d ago against content hash d2e25e9f63ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

project-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 10d 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/project-memory/SKILL.md · 166 lines

How it starts

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

Project Memory

Use project memory to preserve durable project context for humans and future agents.

Project memory is a record of what happened, what was learned, what decisions were made, and what still needs judgment. It is not primarily an agent handoff. Only include handoff or resume instructions when work is incomplete, interrupted, or the user explicitly asks for a handoff.

Project memory lives at:

docs/memory/YYYY-MM-DD/descriptive-slug-memory-YYYY-MM-DD.md

Memory is append-only by default. Create a new file for new work. Do not overwrite, delete, or rewrite prior memory unless the user explicitly asks.

Before Work

For substantial work:

  1. Find the project root.
  2. Check whether docs/memory/ exists.
  3. If it exists, list recent memory files:
find docs/memory -type f -name '*.md' | sort | tail -10
  1. Read the most recent relevant memory files.
  2. Read any source-of-truth docs referenced by those files when they matter for the task.
  3. Briefly summarize the relevant context before acting.

If no memory exists, continue normally. Do not create memory at the start unless the user asks.

After Meaningful Work

Create a new memory file when the session produced context that future humans or agents would be annoyed to rediscover.

Use today's local date and create the dated folder if needed:

docs/memory/YYYY-MM-DD/

Use a lowercase descriptive slug:

docs/memory/2026-05-18/auth-flow-memory-2026-05-18.md

Do not write memory for tiny edits, quick answers, routine formatting, or work that leaves no durable decisions, constraints, verification, or next actions.

What To Capture

Capture durable context, not a transcript:

  • session summary
  • what was learned
  • decisions made
  • open decisions that still need judgment
  • files created or changed
  • source-of-truth docs
  • commands, tests, builds, screenshots, or checks run
  • known constraints, gotchas, and failure modes
  • open questions
  • recommended next work, when useful
  • handoff or resume notes, only when work is incomplete or explicitly handed off

Read the full file on GitHub · 166 lines

Files

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 10d ago First seen · 166 lines · 102 tokens per session scan A d2e25e9f63ba

Subscribe to this mod's changes

project-memory is a skill published in the GitHub repository cobibean/shared-skills-registry-mcp (7 stars, last pushed 2mo ago), licensed MIT. It adds 102 tokens to every session and 965 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-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

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

shellm

Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.

laude-institute/headlong · 49 tokens