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 kitfunso/hippo-memory --skill memorygit clone --depth 1 https://github.com/kitfunso/hippo-memoryWrote 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/kitfunso/hippo-memory/memory)<a href="https://agentmods.dev/skills/kitfunso/hippo-memory/memory"><img src="https://agentmods.dev/badge/skills/kitfunso/hippo-memory/memory/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/kitfunso/hippo-memory/memory"><img src="https://agentmods.dev/badge/skills/kitfunso/hippo-memory/memory.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.00044 | $0.00449 |
| Opus 5.5 | $0.00018 | $0.00180 |
| Sonnet 5.5 | $0.00009 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
memory 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 12d 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.
What it actually says
Hippo Memory
Make your agent's memory work like a brain. Hippo is long-term memory for coding agents. Memories decay over time unless retrieved. Errors stick longer. Sleep consolidates.
At session start (MANDATORY)
Before doing any work, load relevant context:
hippo context --auto --budget 1500
Read the output. These are things the project has learned from past sessions.
When you learn something non-obvious
hippo remember "<the lesson in 1-2 sentences>" --tag <category>
When you hit an error or unexpected failure
hippo remember "<what failed, why, and how you fixed it>" --error
The --error flag doubles the half-life. Hard lessons don't fade quietly.
After completing work successfully
hippo outcome --good
If the recalled memories were irrelevant:
hippo outcome --bad
When stuck or hitting repeated errors
hippo recall "<what's going wrong>" --budget 2000 --why
When making an architectural decision
hippo decide "<decision>" --context "<why>"
Decisions get a recall boost so they surface when relevant, and stay active until superseded.
When migrating or replacing a tool
hippo invalidate "<old tool>" --reason "migrated to <new tool>"
Or let hippo learn --git detect it automatically from migration commits.
After significant coding sessions
hippo learn --git
This scans recent commits, auto-extracts lessons, and invalidates memories about replaced tools.
Export memories
hippo export memories.json
hippo export --format markdown memories.md
Check memory health
hippo status
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.
- 12d ago Changed e27e10857ee8
- 18d ago Changed e035c85ba448
- 1mo ago First seen · 89 lines · 44 tokens per session scan A 876a5a4ead80
memory is a skill published in the GitHub repository kitfunso/hippo-memory (780 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 449 once invoked, about $0.0002 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-30.
Other skills, from other repositories
ama-memory
Use AMA memory in OpenClaw to recall prior context, capture turns, inspect stored state, end sessions, or delete a user's memory when asked.
keymem
Use when the conversation reveals or needs durable knowledge about the user, the project, or an earlier decision — the recall/remember protocol for keymem's associative memory (keys, namespaces, corrections, and the passively surfaced hints).
ama-memory
Use AMA memory in OpenClaw to recall prior context, capture turns, inspect stored state, end sessions, or delete a user's memory when asked.
memory-triage
Persistent long-term memory protocol powered by mem0. Evaluate conversations for durable facts worth storing via memoryadd. Handles identity, preferences, decisions, configurations, rules, projects, and relationships. Loaded by the openclaw-mem0 plugin when skills mode is active.
mem0-cli
Mem0 CLI -- the command-line interface for mem0 memory operations. TRIGGER when: user mentions "mem0 cli", "mem0 command line", "@mem0/cli", "mem0-cli", "pip install mem0-cli", "npm install -g @mem0/cli", or is running mem0 commands in a terminal/shell (mem0 add, mem0 search, mem0 list, mem0 get, mem0 init, mem0…
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…