agent-memory-kit CLAUDE.md

A set of project instructions for developing the agent-memory-kit Claude Code plugin marketplace. It documents paths, setup boundaries, context handling, and rules that must remain consistent.

In plain words
What is it for?
Guiding changes to the memory-kit plugin, its hooks and skills, marketplace documentation, path handling, setup behavior, and language requirements.
Why use it?
It reduces mistakes such as writing into the wrong repository, resolving plugin paths incorrectly, or putting instructions in files the plugin cannot ship.

Instructions file

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.

agentmods
npx agentmods add instructions/awrshift/agent-memory-kit/claude-md
Clone the repo
git clone --depth 1 https://github.com/awrshift/agent-memory-kit
Per session 594 This file is loaded in full into every session.
When invoked 594 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00594 $0.00594
Opus 5 $0.00297 $0.00297
Sonnet 5 $0.00119 $0.00119
Haiku 4.5 $0.00059 $0.00059

Measured yesterday against content hash 1b0ea90728d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-memory-kit CLAUDE.md 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.

Origin

This is a copy

100% identical to claude-memory-kit CLAUDE.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

CLAUDE.md · 45 lines

How it starts

The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Working on Memory Kit

This repo is a Claude Code plugin marketplace, not a memory workspace. The plugin lives in plugins/memory-kit/; .claude-plugin/marketplace.json is the catalog. Users install it into their repositories — nothing here should assume it runs at the project root.

Rules that are easy to get wrong

  • Paths. Anything the plugin ships resolves from ${CLAUDE_PLUGIN_ROOT}; anything about the user's repo resolves from CLAUDE_PROJECT_DIR. Never derive a project root from __file__ — the plugin runs from a cache directory.
  • Never write into a repo that didn't ask. The plugin can be installed user-wide. Scaffolding happens only inside /memory-kit:setup, after a yes.
  • What a plugin cannot ship: CLAUDE.md, .claude/rules/, and any settings.json key other than agent / subagentStatusLine. Context therefore travels via hooks, skills and agents — the working agreement is plugins/memory-kit/context/identity.md, injected at SessionStart.
  • Always-loaded vs on-invoke. A skill body loads only when invoked; a rule without paths: loads every session forever. Put weight in skills and reference/, never in rules.
  • Verify injection by looking at the context, not the code. v5 claimed for a year that the hot cache was always loaded while the hook only measured it. Run the hook and read its output.

Before committing a change to hooks or skills

claude plugin validate ./plugins/memory-kit
CLAUDE_PROJECT_DIR=<test-repo> CLAUDE_PLUGIN_ROOT=$PWD/plugins/memory-kit \
  python3 plugins/memory-kit/hooks/session-start.py <<< '{"source":"startup"}'

Exercise every SessionStart source (startup · resume · compact · fork · clear) and both hook outcomes for protect-tests.py — the profiles are the whole design, and a broken one fails silently.

Docs that must stay true in the same commit

A behaviour change touches docs/CHANGELOG.md; a layer change also touches docs/ARCHITECTURE.md and BOTH readmes — the root README.md (the pitch) and plugins/memory-kit/README.md (the skill table). A change to what a diagram asserts touches docs/ASSETS.md, even when the PNG is not regenerated in the same commit — a stale panel is a lie in the most-read file. VERSION, plugin.json and marketplace.json carry the same version — they have drifted before.

Read the full file on GitHub · 45 lines

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 · 45 lines · 594 tokens per session scan A 1b0ea90728d9

Subscribe to this mod's changes

agent-memory-kit CLAUDE.md is an instructions file published in the GitHub repository awrshift/agent-memory-kit (31 stars, last pushed 2d ago), licensed MIT. It adds 594 tokens to every session, about $0.0030 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to claude-memory-kit CLAUDE.md, differing in 0 lines, and is treated as a copy.