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 instructions/kitfunso/hippo-memory/agents-mdgit clone --depth 1 https://github.com/kitfunso/hippo-memoryWhat 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.00417 | $0.00417 |
| Opus 5 | $0.00209 | $0.00209 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
hippo-memory AGENTS.md 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 2d 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
AGENTS.md - Hippo
Project
hippo-memory, a TypeScript memory system and CLI with UI, integrations, benchmarks, and evaluation harnesses.- Read
README.md,PLAN.md,ROADMAP.md, and relevant docs before broad product or architecture changes.
Commands
npm run build
npm test
npm run build:ui
npm run build:all
npm run smoke:pack
npm run smoke:openclaw-install
Rules
- Preserve public CLI and package APIs unless the user asks for a breaking change.
- Document public APIs with JSDoc.
- Prefer focused tests in
tests/or nearby integration/eval harnesses before changing memory behavior. - Do not commit generated
dist/or UI build output unless the repo expects it for a release. - Use Hippo memory commands when useful, but do not store secrets.
Never Do
- Never store secrets, API keys, tokens, raw private emails, or sensitive personal data in Hippo memories.
- Never break the public
hippoCLI command names without a migration path. - Never auto-graduate long-term lessons without evidence and rationale.
- Never delete memory history when archiving or weakening would preserve recoverability.
- Never ship release changes without
npm run build:all.
Project Memory (Hippo)
At the start of every task, run:
hippo context --auto --budget 1500
Read the output before writing any code.
On errors or unexpected behaviour:
hippo remember "<description of what went wrong>" --error
On task completion:
hippo outcome --good
When Hippo's Codex wrapper is installed, session-end capture runs automatically. If the wrapper is not installed, capture a brief summary manually:
hippo capture --stdin <<< '<decisions, errors, lessons — 2-5 bullets>'
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.
- 2d ago First seen · 56 lines · 417 tokens per session scan A 3d40587540e7
hippo-memory AGENTS.md is an instructions file published in the GitHub repository kitfunso/hippo-memory (735 stars, last pushed 8d ago), licensed MIT. It adds 417 tokens to every session, about $0.0021 per session on Opus 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.