Borrowing it
Nothing to install: this file belongs to kitfunso/hippo-memory. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kitfunso/hippo-memory/master/.claude/commands/hippo-feature.mdgit 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/commands/kitfunso/hippo-memory/hippo-feature)<a href="https://agentmods.dev/commands/kitfunso/hippo-memory/hippo-feature"><img src="https://agentmods.dev/badge/commands/kitfunso/hippo-memory/hippo-feature/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/commands/kitfunso/hippo-memory/hippo-feature"><img src="https://agentmods.dev/badge/commands/kitfunso/hippo-memory/hippo-feature.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.00017 | $0.01213 |
| Opus 5.5 | $0.00007 | $0.00485 |
| Sonnet 5.5 | $0.00003 | $0.00243 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
hippo-feature 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 29d 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are entering hippo-feature mode to build a new memory mechanic from RESEARCH.md. Follow the eval pyramid strictly. Skipping tiers wastes hours of LoCoMo time.
The eval pyramid (non-negotiable)
| Tier | Harness | Time | When |
|---|---|---|---|
| 1 | benchmarks/micro/run.py |
~30s | Every code change |
| 2 | benchmarks/locomo/run.py --conversations 1 --sample 10 --score-mode evidence |
~5-10 min | Before opening a PR |
| 3 | LoCoMo full | ~85 min evidence / ~6h judge | Release gate only |
If a feature shows no Tier 1 signal, do not proceed to Tier 2. If Tier 2 shows a regression, do not run Tier 3.
The loop
0. Pick the feature
If $ARGUMENTS names a feature (e.g. acc-evc, vmpfc-value, dlpfc-goals, vlpfc-gate, pineal-salience-v2), use it. Otherwise read the PFC priority table in RESEARCH.md (lines ~459-466) and propose the top three by effort × benchmark delta. Wait for user confirmation.
1. RED — Write the failing micro fixture FIRST
- Drop a fixture at
benchmarks/micro/fixtures/<feature>.jsonwith shape:{ "name": "<feature>-<aspect>", "mechanic": "<feature>", "description": "<one sentence: what behaviour this proves>", "remembers": [...], "queries": [{"q": "...", "must_contain_any": [...], "top_k": N}] } - The fixture must encode behaviour the current system cannot satisfy. If it passes on main today, the fixture is wrong — make it harder.
- Run
python benchmarks/micro/run.py --filter <feature>and confirm it fails. - Save the failing baseline:
python benchmarks/micro/run.py --out benchmarks/micro/results/baseline-<feature>.json.
2. PLAN — Outside voice on non-trivial features
Per global CLAUDE.md outside-voice rule: if the feature touches schema, retrieval ranking, or storage (i.e. anything in the PFC priority table), run /plan-eng-review on the implementation plan before writing code. Skip only for one-line tweaks.
3. GREEN — Minimum implementation
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.
- 29d ago Changed 8ebf6c5c1dda
- 1mo ago First seen · 99 lines · 17 tokens per session scan A b27f875f6106
hippo-feature is a command published in the GitHub repository kitfunso/hippo-memory (785 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,213 once invoked, about $0.0001 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 commands, from other repositories
cpp-test
Enforce TDD workflow for C++. Write GoogleTest tests first, then implement. Verify coverage with gcov/lcov.
go-test
Go TDD workflow with table-driven tests.
help
Get help with EverMem plugin setup and available commands.
recall
Ask Honcho what it remembers about a topic from past sessions.
tdd
Test-driven change — write the failing test first, then implement.
tree-ring-certify
Generate Tree Ring harness or recall-quality evidence without confusing it with the full framework release suite.