Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add awrshift/agent-memory-kit/plugin install 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/skills/awrshift/agent-memory-kit/setup)<a href="https://agentmods.dev/skills/awrshift/agent-memory-kit/setup"><img src="https://agentmods.dev/badge/skills/awrshift/agent-memory-kit/setup/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/skills/awrshift/agent-memory-kit/setup"><img src="https://agentmods.dev/badge/skills/awrshift/agent-memory-kit/setup.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.00119 | $0.03998 |
| Opus 5.5 | $0.00048 | $0.01599 |
| Sonnet 5.5 | $0.00024 | $0.00800 |
| Haiku 4.5 | $0.00012 | $0.00400 |
Grade B, and why
setup scanned grade B with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
[ -f "$HOOK" ] || HOOK=$(find ~/.claude/plugins -path '*memory-kit*' -name session-start.py | head -1) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
docker, curl or an interpreter (`Bash(git *)`, `Bash(node *)`, `Bash(python3 *)`, `Bash(*)`): How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/memory-kit:setup — adopt the kit in an existing repository
The plugin ships behaviour; the repository owns the state. This skill creates that state — always asking before the first write, and never touching files the repo already has.
Running without a user who can answer (a headless or -p run)? Then "offer" means skip and
report: take the documented default where one exists, install nothing that the skill marks as
opt-in, and finish with a list of what was deliberately not installed and what question is still
open. Never invent a preference on the user's behalf and never present a skipped step as done.
Running under a host other than Claude Code (Codex and others load this skill too)?
${CLAUDE_PLUGIN_ROOT} will not expand there — resolve every plugin path in this skill
relative to this SKILL.md file's own location (../../ is the plugin root), and skip the
Claude-Code-only steps (settings.json keys, /context) with a one-line note.
Step 0 — look before you write
Report in two lines what already exists: .claude/memory/MEMORY.md, context/handoffs/,
knowledge/, projects/, an existing documentation home (docs/, doc/, documentation/),
.claude/settings.json, .gitignore, and whether this repo already holds work of its own —
code, or documents other than a bare README (a real project) — or is effectively empty (a fresh
memory workspace). Being a git repo decides nothing; content does. Everything after this is a proposal the user
confirms once, not a sequence of prompts.
Step 1 — the shared memory layers
These four are shared across every project in the repo. Create only what is missing, copying
from ${CLAUDE_PLUGIN_ROOT}/templates/:
| Path | From | Purpose |
|---|---|---|
.claude/memory/MEMORY.md |
templates/MEMORY-TEMPLATE.md |
the hot cache the hook injects every session |
context/handoffs/HANDOFF-TEMPLATE.md |
templates/HANDOFF-TEMPLATE.md |
the per-session note format |
knowledge/index.md |
templates/workspace/knowledge-index.md |
the catalog of deep memory |
knowledge/concepts/.gitkeep |
— | where promoted patterns land |
.claude/state/.gitkeep |
— | hook bookkeeping (gitignored) |
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 42d6c9a2e960
- 18d ago Changed 587c3c3b80b6
- 20d ago Changed · +33 lines · +26 tokens per session scan D → B 57296888c814
- 27d ago Changed · +3 lines 63a8bf8e08c2
- 1mo ago Changed · +6 lines 09ab345c0477
- 1mo ago First seen · 202 lines · 93 tokens per session scan D 9d3639499ca1
setup is a skill published in the GitHub repository awrshift/agent-memory-kit (34 stars, last pushed 9d ago), licensed MIT. It adds 119 tokens to every session and 3,998 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
aictx
Use this skill when working in a repository that uses AICTX for repo-local operational continuity. Prefer AICTX MCP tools when available, fall back to CLI commands, resume before substantial work, and finalize factual continuity after work.
kayba-ace
This skill ships learnfromtraces.py, a script that reads OpenClaw session transcripts, feeds them through the ACE learning pipeline, and writes an updated skillbook to disk.
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.
alive:capture-context
Use when external content arrives in the session — emails, transcripts, screenshots, documents, files, or in-session research worth keeping. Also use when there's nothing obvious to capture — the skill checks 03Inbox/ for unrouted files and enters inbox scan mode. Stores raw content, routes to bundles, extracts tasks…
alive:load-context
The human mentions a walnut to work on, asks about a specific venture/experiment/project, or wants to check status — not just explicit 'load X'. Load the brief pack (3 files), resolve the people involved, check the active bundle — then surface one observation and ask what to work on. Context loads in tiers: walnut and…