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.
git clone --depth 1 https://github.com/awrshift/agent-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/plugins/awrshift/agent-memory-kit/memory-kit)<a href="https://agentmods.dev/plugins/awrshift/agent-memory-kit/memory-kit"><img src="https://agentmods.dev/badge/plugins/awrshift/agent-memory-kit/memory-kit/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/plugins/awrshift/agent-memory-kit/memory-kit"><img src="https://agentmods.dev/badge/plugins/awrshift/agent-memory-kit/memory-kit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 8d 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.
What it actually says
{
"name": "memory-kit",
"displayName": "Memory Kit",
"version": "7.2.3",
"description": "Persistent memory for your agent as plain files in your folder: a hot cache injected every session and held under three size caps, per-session handoffs, and promotion into knowledge articles and rules only on your yes. Carries the builder's layers too — executor/recon/idea-validator agents, session review, second opinion, agent QA and a system audit — all lazy-loaded skills you only pay for on use. Installs into any existing repository.",
"author": {
"name": "awrshift",
"url": "https://github.com/awrshift"
},
"homepage": "https://github.com/awrshift/agent-memory-kit",
"repository": "https://github.com/awrshift/agent-memory-kit",
"documentationUrl": "https://github.com/awrshift/agent-memory-kit/blob/main/docs/ARCHITECTURE.md",
"supportUrl": "https://github.com/awrshift/agent-memory-kit/issues",
"privacyPolicyUrl": "https://github.com/awrshift/agent-memory-kit/blob/main/PRIVACY.md",
"termsOfServiceUrl": "https://github.com/awrshift/agent-memory-kit/blob/main/LICENSE",
"license": "MIT",
"keywords": [
"memory",
"context-management",
"session-handoff",
"knowledge-base",
"orchestration",
"agent-qa",
"system-audit"
]
}
What it installs
The manifest is a name and a version. 10 skills, 4 agents, 4 hooks travel with it, and installing the plugin installs all of them — 1,943 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill system-audit A 225 tokens
- Skill code-sync A 119 tokens
- Skill document A 170 tokens
- Skill memory-audit A 137 tokens
- Skill qa-sweep A 199 tokens
- Skill session-review A 149 tokens
- Skill close-session A 64 tokens
- Skill second-opinion A 130 tokens
- Skill setup B 119 tokens
- Skill tour B 50 tokens
- Agent executor A 207 tokens
- Agent recon A 95 tokens
- Agent idea-validator B 97 tokens
- Agent qa B 182 tokens
- Hook PreToolUse A not measured
- Hook SessionEnd A not measured
- Hook PreCompact A not measured
- Hook SessionStart A not measured
What ships with it
1 file beside plugin.json 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.
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.
- 8d ago Changed · +4 lines b08d31ab69c2
- 18d ago Changed a55ade123e2c
- 20d ago Changed 86e0d5847f93
- 22d ago Changed fe41baac3aa1
- 26d ago Changed e65a4571b610
- 27d ago Changed fe90268a0796
- 1mo ago Changed 737af4961766
- 1mo ago First seen · 23 lines scan A 64a1d4349d9b
memory-kit is a plugin published in the GitHub repository awrshift/agent-memory-kit (34 stars, last pushed 9d ago), 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.
Other plugins, from other repositories
aictx
Use AICTX repo-local operational continuity in Claude Code.
navigator
Finish What You Start - Sessions that last, AI that learns, Features that ship. Context engineering + Theory of Mind + Knowledge Graph + Loop Mode + Task Mode. Features Project Knowledge Graph (unified search, experiential memory), unified workflow orchestration, auto-update on session start, ToM-based verification…
alive
Local, user-owned context for Claude Code. Keep your work in files you control.
claude-ryzome
Ryzome — AI context library. Create, retrieve, and manage canvases and documents for externalizing agent working memory.
eos
eos. Your AI finally remembers your codebase.
llm-handoff
Cross-LLM context handoff — creates a complete handover.md so any LLM can continue your work without mistakes. Auto-triggers before context compaction.