Borrowing it
Nothing to install: this file belongs to awrshift/agent-memory-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/awrshift/agent-memory-kit/main/CLAUDE.mdgit 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/instructions/awrshift/agent-memory-kit/claude-md)<a href="https://agentmods.dev/instructions/awrshift/agent-memory-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/awrshift/agent-memory-kit/claude-md/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/instructions/awrshift/agent-memory-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/awrshift/agent-memory-kit/claude-md.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.00833 | $0.00833 |
| Opus 5.5 | $0.00333 | $0.00333 |
| Sonnet 5.5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00083 | $0.00083 |
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 21d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- claude-memory-kit CLAUDE.md — 100% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 55 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 fromCLAUDE_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 anysettings.jsonkey other thanagent/subagentStatusLine. Context therefore travels via hooks, skills and agents — the working agreement isplugins/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 andreference/, never in rules. - This checkout is live on the maintainer's machine. The marketplace is registered as a local
DIRECTORY, so every kit project loads
plugins/memory-kit/IN PLACE from here at session start — not from~/.claude/plugins/cache/, whateverinstalled_plugins.jsonrecords (verified 2026-09-25 in a debug log). A branch checkout orresethere changes all of them at once: experiment in a separate worktree withclaude --plugin-dir <worktree>/plugins/memory-kit. - 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.
And mind the transport: Claude Code caps ONE hook's
additionalContextat 10,000 characters — over it the model gets a file path and a 2,000-char preview, so a hook can print the hot cache and the model still never see it (true of every kit repo until 7.2). Each--part Noutput must stay ≤ 10,000; the proof is a model-level probe (claude -pwith tools disallowed, asked to quote a MEMORY.md line), not the hook's stdout.
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.
- 21d ago Changed · +10 lines · +239 tokens per session 13a3049fcf3a
- 1mo ago First seen · 45 lines · 594 tokens per session scan A 1b0ea90728d9
agent-memory-kit CLAUDE.md is an instructions file published in the GitHub repository awrshift/agent-memory-kit (34 stars, last pushed 9d ago), licensed MIT. It adds 833 tokens to every session, about $0.0033 per session on Opus 5.5. 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 instructions, from other repositories
pluribus copilot-instructions.md
Instructions for caioribeiroclw-pixel/pluribus, covering project, stack, conventions, constraints and goals.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.