awrshift

Agent Memory Kit — Documentation skill for Claude Code

Documentation community

One memory for every coding agent — plain markdown in your repo.

How to install Agent Memory Kit

This entry records only its repository, not the path inside it, so there is no exact command to give. Open awrshift/agent-memory-kit and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Agent Memory Kit does

One memory for every coding agent — plain markdown in your repo. Injected on Claude Code & Cursor, skills on Codex & Copilot, plugin for OpenCode. Dated, capped, audited: agent memory that doesn't rot. Session handoffs, human-approved promotion into knowledge and rules, plus orchestration and QA layers.

Alternatives in Documentation

会话管理（Session Manager）需求文档（PRD / Markdown） — 目标：对 Codex / Claude Code 的本地会话记录进行可视化管理，并提供“一键复制 / 一键终端恢复”能力 31.7k ★
Hash — by hashintel - Features comprehensive repository structure breakdown with strong emphasis on coding standards 1.4k ★
Qmd Skill — A Codex/Clawd skill definition for qmd (Quick Markdown Search) 673 ★

README

![Memory Kit](.github/assets/og-banner-one-memory.png)

Memory Kit

**One memory for every coding agent.** **Plain markdown in your repository — injected on Claude Code, Cursor and OpenCode, followed by Codex and Copilot, readable by anything. Dated, capped, audited: it doesn't rot.**

[![Version](https://img.shields.io/github/v/release/awrshift/agent-memory-kit?label=version&color=CFEF4A&cacheSeconds=1800)](https://github.com/awrshift/agent-memory-kit/releases) [![License: MIT](https://img.shields.io/badge/License-MIT-55503E?labelColor=55503E&color=55503E)](LICENSE) [![Works with](https://img.shields.io/badge/works_with-Claude_Code_·_Cursor_·_Codex_·_Copilot_·_OpenCode-CFEF4A)](docs/specs/README.md)

*"I wake up already knowing where we left off."* — the agent this kit builds.

Install

In Claude Code, into a repository you already have:

/plugin marketplace add awrshift/agent-memory-kit
/plugin install memory-kit@memory-kit
/memory-kit:setup

Work as usual; say `/memory-kit:close-session` when you're done. That's the whole loop — no database, no service, no extra cost. Setup reads what your repo already has and **proposes before writing anything**; your `CLAUDE.md` stays yours. Codex and Cursor install from the same repository — see [Works with your agents](#works-with-your-agents).

Upgrading later — two commands, and the second needs the full id

claude plugin marketplace update memory-kit     # refresh the catalog
claude plugin update memory-kit@memory-kit      # the bare name resolves to nothing

Restart the session to apply. Upgrades never touch your repo — memory, handoffs and knowledge live in your files, not in the plugin.

The problem

Every session starts from zero: yesterday you locked the brand voice, today you explain it again. What your tools do remember is scattered — Claude Code's notes in one silo, Cursor's in another, none of it in your repo, none of it yours. And memory