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.
npx skills add awrshift/claude-memory-kit --skill memory-auditgit clone --depth 1 https://github.com/awrshift/claude-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/claude-memory-kit/memory-audit)<a href="https://agentmods.dev/skills/awrshift/claude-memory-kit/memory-audit"><img src="https://agentmods.dev/badge/skills/awrshift/claude-memory-kit/memory-audit/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/claude-memory-kit/memory-audit"><img src="https://agentmods.dev/badge/skills/awrshift/claude-memory-kit/memory-audit.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.00988 |
| Opus 5.5 | $0.00048 | $0.00395 |
| Sonnet 5.5 | $0.00024 | $0.00198 |
| Haiku 4.5 | $0.00012 | $0.00099 |
Grade A, and why
memory-audit 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 2mo 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.
This is a copy
100% identical to memory-audit — 44 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory audit — the surgical one-file pass
This is the cap-trip response, not the daily ritual. /memory-kit:close-session runs every
session and captures; this runs when the hot cache has actually outgrown itself and something
must LEAVE it. Keeping them separate is the point: a daily ritual that also has to do surgery
becomes a ritual people skip.
Always pause for approval before writing. The user talks; you write — including here.
Inputs
.claude/memory/MEMORY.md— read in full.knowledge/concepts/*.md— filenames + first 5 lines, for duplicate detection (the directory may not exist yet; the first move creates it).context/handoffs/— to confirm a session narrative already lives there → drop, not move.
Step 1 — classify every section
Scan by ## heading. For each, count lines and mark exactly one action:
| Mark | When |
|---|---|
move (create) |
a settled pattern (confirmed on 3+ distinct dates) with >25 lines of reference detail |
move (merge) |
same, but a concept article on the topic already exists |
drop |
a per-session chronicle — it already lives in a handoff; distil at most one settled line |
update in-place |
stale: names a deleted file, a closed ticket, a superseded decision |
simplify |
true and useful, but three times longer than it needs to be |
keep |
earns its lines |
Step 2 — the move plan (a table, never prose)
| # | Section | Lines | Action | Target | Reason |
|---|---|---|---|---|---|
| 1 | … | N | move / merge / drop / simplify / keep | knowledge/concepts/<slug>.md or — |
… |
Close the table with: estimated line savings, and the projected line/byte count afterwards against the caps (180 lines / 32 KB / 3000 chars per line).
Step 3 — PAUSE
Print the plan and ask for approval. Wait for an explicit yes or edits. No writes before that.
Step 4 — execute the approved moves, atomically
- move (create): write
knowledge/concepts/<slug>.mdwith frontmatter matchingknowledge/index.md's spec, then add its one-line entry to that index in the same pass. - move (merge): append under a
### From MEMORY.md (YYYY-MM-DD)header — never duplicate a section that already says the same thing. - in MEMORY.md: replace the moved section with a one-line pointer plus a one-line teaser. A move without a pointer orphans the content — that is the failure this audit exists to prevent.
- drop: delete; keep at most one distilled line.
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.
- 2mo ago First seen · 78 lines · 119 tokens per session scan A 04a91efc3646
memory-audit is a skill published in the GitHub repository awrshift/claude-memory-kit (31 stars, last pushed 2mo ago), licensed MIT. It adds 119 tokens to every session and 988 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to memory-audit, differing in 44 lines, and is treated as a copy.
Other skills, from other repositories
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
adr-ops
Author, index, and lint Architecture Decision Records — append-only memory that recovers the WHY behind a system's shape. Triggers on: adr, architecture decision record, decision log, record this decision, supersede an adr, why was this decided, adr template, next adr number.
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.
hive-mind-advanced
Queen-led collective-intelligence coordination with consensus mechanisms and persistent shared memory. Use when orchestrating a large swarm of agents under a lead coordinator, building consensus across agents, or maintaining durable cross-agent memory.
creator-productivity
Task management and workspace memory for creative work sessions. Manages a TASKS.md file for project tracking, a two-tier memory system (CREATOR.md + creator-memory/), and a daily sprint structure. Use when organizing creative projects, tracking content tasks, or starting a focused work session.
memory-prune
Manual reviewable prune of stale memory entries. Lists project entries older than 30 days with content preview; Frank decides per-entry [keep | archive | pin]. Keeps MEMORY.md under the auto-load 200-line truncation. Use when MEMORY.md exceeds 180 lines or session-end after a heavy work week.