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/agent-memory-kit --skill memory-auditgit 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/skills/awrshift/agent-memory-kit/memory-audit)<a href="https://agentmods.dev/skills/awrshift/agent-memory-kit/memory-audit"><img src="https://agentmods.dev/badge/skills/awrshift/agent-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/agent-memory-kit/memory-audit"><img src="https://agentmods.dev/badge/skills/awrshift/agent-memory-kit/memory-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00137 | $0.01596 |
| Opus 5.5 | $0.00055 | $0.00638 |
| Sonnet 5.5 | $0.00027 | $0.00319 |
| Haiku 4.5 | $0.00014 | $0.00160 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- memory-audit — 100% identical, 38 lines differ
How it starts
The opening of the file, as written. The whole thing — 98 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.- The newest
context/audits/memory-audit-deferred-*.md, if one exists — the candidates the previous audit left; start from them.
Step 1 — classify every section
Scan by ## heading (and ### inside a long section). For each, count lines and mark exactly
one action. Also read the project's CLAUDE.md, the .claude/rules/*.md without paths: and
the plugin's reference/ titles — you need them for restates-rule.
| 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 |
session-block |
the heading names a session or a date, not a topic (### s66 (2026-09-25), ## Session 65 wrap, ## Findings [date] — …; the SessionStart hook flags these) → dissolve by topic: each settled lesson → one line under its topic heading or a concept; the rest → drop |
drop |
a per-session chronicle — it already lives in a handoff; distil at most one settled line |
restates-rule |
the entry says what CLAUDE.md, an always-loaded rule or a reference/ file already says → drop, or one pointer line if the link is not obvious. The agent reads those files every session; a second copy only drifts |
point to SSOT |
a derivable number — price, count, version, limit — whose source of truth lives elsewhere (a price table in code, a config, a vendor page) → replace the value with a pointer to that source (reference/doc-governance.md R1). A copied number outlives the thing it described |
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 |
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 b5da6d926ac5
- 21d ago Changed · +16 lines · +18 tokens per session d7cede837c69
- 22d ago Changed · +4 lines e7fdd7c7c686
- 1mo ago First seen · 78 lines · 119 tokens per session scan A 04a91efc3646
memory-audit is a skill published in the GitHub repository awrshift/agent-memory-kit (34 stars, last pushed 9d ago), licensed MIT. It adds 137 tokens to every session and 1,596 once invoked, about $0.0005 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 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…