awrshift

Claude Memory Kit — Security skill for Claude Code

Security community

Memory for Claude Code that survives the session boundary — install the plugin into any repo: a hot cache injected every session under three hook-enforced caps, per-session handoffs, audit-driven prom.

How to install Claude Memory Kit

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

What Claude Memory Kit does

Alternatives in Security

Security Guidance — Hook that warns about command injection, XSS, and unsafe patterns 14k ★
Security Guardian — Comprehensive security analysis for RTK CLI tool, focusing on command injection, shell escaping, hook security 11.9k ★
Sanyuan Skills — Expert code review skill: SOLID, security, performance, error handling, boundary conditions 2.7k ★

README

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

Claude Memory Kit

**The memory plugin for Claude Code.** **Your agent remembers every client, every brief, every decision — across sessions. Three lines to install, nothing to maintain.**

[![Version](https://img.shields.io/github/v/release/awrshift/claude-memory-kit?label=version&color=CFEF4A&cacheSeconds=1800)](https://github.com/awrshift/claude-memory-kit/releases) [![License: MIT](https://img.shields.io/badge/License-MIT-55503E?labelColor=55503E&color=55503E)](LICENSE) [![Claude Code](https://img.shields.io/badge/Claude_Code-plugin-CFEF4A)](https://code.claude.com/docs/en/plugins)

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

**Install it into a repository you already have:**

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

Then work as usual, and type `/memory-kit:close-session` when you're done. That's the whole loop. Free — it runs on your existing Claude Pro or Max subscription and calls nothing else.

**Upgrading later** takes two steps, and the second one needs the FULL `plugin@marketplace` identifier — the bare name resolves to nothing and the CLI answers `Plugin "memory-kit" not found`:

claude plugin marketplace update memory-kit     # refresh the catalog
claude plugin update memory-kit@memory-kit      # then the plugin itself

Restart the session to apply. Your repository is untouched by an upgrade — memory, handoffs and knowledge live in your repo, never in the plugin — so `/memory-kit:setup` does not need re-running.

The problem

Every session starts from zero. Yesterday you locked the brand voice; today you explain it again. Last week you found the right angle; this week you can't reconstruct how. The first ten minutes of every session go to re-explaining what Claude **already knew**.

Built for **people running many projects or clients** — one install per repository, eac