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 agentmods add skills/rmarquesa/agentmemory-offline/agentmemory-hooksnpx skills add rmarquesa/agentmemory-offline --skill agentmemory-hooksgit clone --depth 1 https://github.com/rmarquesa/agentmemory-offlineWrote 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/rmarquesa/agentmemory-offline/agentmemory-hooks)<a href="https://agentmods.dev/skills/rmarquesa/agentmemory-offline/agentmemory-hooks"><img src="https://agentmods.dev/badge/skills/rmarquesa/agentmemory-offline/agentmemory-hooks.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00371 |
| Opus 5 | $0.00021 | $0.00186 |
| Sonnet 5 | $0.00008 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
agentmemory-hooks 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 3d 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 agentmemory-hooks — 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.
What it actually says
The Claude Code plugin registers lifecycle hooks so memory is captured automatically. You do not have to call memory_save for routine work; the hooks observe tool use, prompts, and session boundaries and write observations for you.
Quick start
Install the plugin and the hooks register themselves:
/plugin marketplace add rohitg00/agentmemory
/plugin install agentmemory
Watch observations land live at http://localhost:3113.
What the hooks do
- Session start and end frame each unit of work and let
handoffresume it. - Tool-use hooks capture what changed and why, the raw material for
recallandrecap. - Prompt-submit captures intent. Pre-compact preserves context before the host trims it.
- A post-commit hook links commits to sessions, which powers
commit-contextandcommit-history.
Important
- Capture is on by default and is zero-LLM. Turning observations into LLM summaries (
AGENTMEMORY_AUTO_COMPRESS) and injecting them back into context (AGENTMEMORY_INJECT_CONTEXT) are separate opt-ins because they spend tokens. - If observations are missing, confirm the plugin is enabled and the server is running. See ../_shared/TROUBLESHOOTING.md.
See also
- agentmemory-config for the capture and injection flags.
- The handoff, recap, and session-history skills consume what these hooks record.
Reference
The exact registered hook events live in REFERENCE.md, generated from plugin/hooks/hooks.json.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 40 lines · 42 tokens per session scan A 1ce38dac7869
agentmemory-hooks is a skill published in the GitHub repository rmarquesa/agentmemory-offline (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 371 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agentmemory-hooks, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
plur-memory
Persistent learning for AI agents. Open engram format. Your agent learns from corrections, remembers across sessions, and transfers knowledge across domains.
plur-session-end
Extract durable learnings at the end of a session. Saves corrections, preferences, and codebase patterns as engrams — nothing ephemeral, nothing sensitive.
plur-memory
Your memory stays on your machine. No cloud, no tracking, no API key. PLUR makes your OpenClaw remember — and shares that memory with every other tool you use.
compartmentalize
Sweep this conversation and save everything potentially worth knowing again into Compartment, the encrypted memory vault. Run it before compacting or summarizing so nothing is lost to the summary, or on its own at any point to bank the session.
paxm
Recall or remember durable project context with paxm.
reduce
Use when asked to simplify, clean up, tidy, or refactor code for clarity without changing what it does, or when the user says "simplify this", "clean this up", "make it readable", "reduce the complexity", or "tidy this". Behavior-preserving only; not a bug or security audit (use bug-hunt or security-sweep for those).