Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add awrshift/claude-memory-kit/plugin install memory-kitWrote 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/awrshift/claude-memory-kit/setup)<a href="https://agentmods.dev/skills/awrshift/claude-memory-kit/setup"><img src="https://agentmods.dev/badge/skills/awrshift/claude-memory-kit/setup/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.
<a href="https://agentmods.dev/skills/awrshift/claude-memory-kit/setup"><img src="https://agentmods.dev/badge/skills/awrshift/claude-memory-kit/setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00093 | $0.02642 |
| Opus 5.5 | $0.00037 | $0.01057 |
| Sonnet 5.5 | $0.00019 | $0.00528 |
| Haiku 4.5 | $0.00009 | $0.00264 |
Grade D, and why
setup scanned grade D with 2 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
[ -f "$HOOK" ] || HOOK=$(find ~/.claude/plugins -path '*memory-kit*' -name session-start.py | head -1) Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"Bash(rm -rf:*)" How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/memory-kit:setup — adopt the kit in an existing repository
The plugin ships behaviour; the repository owns the state. This skill creates that state — always asking before the first write, and never touching files the repo already has.
Running without a user who can answer (a headless or -p run)? Then "offer" means skip and
report: take the documented default where one exists, install nothing that the skill marks as
opt-in, and finish with a list of what was deliberately not installed and what question is still
open. Never invent a preference on the user's behalf and never present a skipped step as done.
Step 0 — look before you write
Report in two lines what already exists: .claude/memory/MEMORY.md, context/handoffs/,
knowledge/, projects/, an existing documentation home (docs/, doc/, documentation/),
.claude/settings.json, .gitignore, and whether this repo already holds work of its own —
code, or documents other than a bare README (a real project) — or is effectively empty (a fresh
memory workspace). Being a git repo decides nothing; content does. Everything after this is a proposal the user
confirms once, not a sequence of prompts.
Step 1 — the shared memory layers
These four are shared across every project in the repo. Create only what is missing, copying
from ${CLAUDE_PLUGIN_ROOT}/templates/:
| Path | From | Purpose |
|---|---|---|
.claude/memory/MEMORY.md |
templates/MEMORY-TEMPLATE.md |
the hot cache the hook injects every session |
context/handoffs/HANDOFF-TEMPLATE.md |
templates/HANDOFF-TEMPLATE.md |
the per-session note format |
knowledge/index.md |
templates/workspace/knowledge-index.md |
the catalog of deep memory |
knowledge/concepts/.gitkeep |
— | where promoted patterns land |
.claude/state/.gitkeep |
— | hook bookkeeping (gitignored) |
Step 1b — the project layer (projects/<name>/)
The four layers above hold MEMORY. The work's own documents — tasks, specs, research, decisions,
QA — belong to a PROJECT, and the kit is multi-project by design: one folder per client or
product, so that a decision ledger, a findings registry and a QA protocol each count and describe
exactly ONE thing. This applies to a single-product code repository too — it simply has one
project folder, named after the product. (Earlier versions told you to skip projects/ in a code
repo. That left specs, backlogs and research with no home, and they scattered into the repo root.)
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.
- 1mo ago First seen · 188 lines · 93 tokens per session scan D e99c07778268
setup is a skill published in the GitHub repository awrshift/claude-memory-kit (31 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 2,642 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.
adr-ops
Author, index, and lint Architecture Decision Records — append-only memory that recovers the WHY behind a system's shape. Triggers on: adr, architecture decision record, decision log, record this decision, supersede an adr, why was this decided, adr template, next adr number.
hive-mind-advanced
Queen-led collective-intelligence coordination with consensus mechanisms and persistent shared memory. Use when orchestrating a large swarm of agents under a lead coordinator, building consensus across agents, or maintaining durable cross-agent memory.
creator-productivity
Task management and workspace memory for creative work sessions. Manages a TASKS.md file for project tracking, a two-tier memory system (CREATOR.md + creator-memory/), and a daily sprint structure. Use when organizing creative projects, tracking content tasks, or starting a focused work session.
memory-prune
Manual reviewable prune of stale memory entries. Lists project entries older than 30 days with content preview; Frank decides per-entry [keep | archive | pin]. Keeps MEMORY.md under the auto-load 200-line truncation. Use when MEMORY.md exceeds 180 lines or session-end after a heavy work week.