memory-kit

A persistent memory plugin for coding agents that keeps selected knowledge across separate sessions, along with optional coordination and quality-checking tools.

In plain words
What is it for?
Maintaining a session memory cache, handing work between sessions, promoting trusted information into shared knowledge and rules, and optionally coordinating agents or checking their work.
Why use it?
It preserves useful context and handoffs after a session ends, reducing the need to rediscover project details.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add awrshift/agent-memory-kit
agentmods
npx agentmods add plugins/awrshift/agent-memory-kit/marketplace
Clone the repo
git clone --depth 1 https://github.com/awrshift/agent-memory-kit

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

memory-kit 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 yesterday.

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.

.claude-plugin/marketplace.json · 28 lines

What it actually says

{
  "name": "memory-kit",
  "owner": {
    "name": "awrshift",
    "url": "https://github.com/awrshift/agent-memory-kit"
  },
  "description": "Memory for coding agents that survives the session boundary — and the builder's layers distilled from a year of daily production use.",
  "plugins": [
    {
      "name": "memory-kit",
      "source": "./plugins/memory-kit",
      "description": "Persistent memory for coding agents: a hot cache under three size caps, per-session handoffs, agent-audited promotion into knowledge and rules — plus the optional orchestration and QA layers as skills you only ever see when you invoke them. Installs into any existing repository.",
      "version": "6.5.0",
      "author": {
        "name": "awrshift"
      },
      "keywords": [
        "memory",
        "context-management",
        "session-handoff",
        "knowledge-base",
        "orchestration",
        "agent-qa"
      ]
    }
  ]
}
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. yesterday First seen · 28 lines scan A fd1fe7c65f80

Subscribe to this mod's changes

memory-kit is a plugin published in the GitHub repository awrshift/agent-memory-kit (31 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories