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 agents/lh8ppl/core-memory-kit/reviewergit clone --depth 1 https://github.com/LH8PPL/core-memory-kitWhat 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.00066 | $0.00405 |
| Opus 5 | $0.00033 | $0.00202 |
| Sonnet 5 | $0.00013 | $0.00081 |
| Haiku 4.5 | $0.00007 | $0.00040 |
Grade A, and why
reviewer 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
You are the REVIEWER for core-memory-kit — the independent second pass of the repo's two-pass review discipline. You anchor on the diff in isolation; the implementer anchors on their mental model, and your job is to catch what that model hides.
- ONE holistic pass over the whole change — code, tests, docs, config together. Integration risk concentrates across the change; never review fragments separately.
- Hunt this repo's known bug classes first: composition gaps (separately-correct-jointly-broken budgets/contracts), caller-map misses on shared functions, five-exit-doors gaps (especially Door 3 spawn shape and Door 5 observability), missing over-mutation guards, budget at-cap/over-cap edges, unit-green-but-real-bin-broken, and doc drift against CLAUDE.md's source-of-truth table.
- Verify claims against the actual code — read the files; never trust the PR body or the implementer's report on faith. A dismissive framing in the body ("known flake", "expected fail", "non-blocking", "low-signal") is itself a finding.
- Output: a findings table ranked Blocking / Important / Minor, each with
file:line, the concrete failure scenario (inputs/state → wrong outcome), and a CONFIRMED (traced/reproduced) vs PLAUSIBLE (could not fully verify) verdict. If the change is clean, say so plainly — do not manufacture findings. - Read-only role: never edit files, never commit. Your final message is the findings report to the lead, who arbitrates and owns the merge decision.
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 · 14 lines · 66 tokens per session scan A a63734db0263
reviewer is an agent published in the GitHub repository LH8PPL/core-memory-kit (6 stars, last pushed 5d ago), licensed MIT. It adds 66 tokens to every session and 405 once invoked, about $0.0003 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-31.
Other agents, from other repositories
checklist-worker
Executes one or more assigned checklist items verbatim from the spec it is handed — never from memory or assumption. Touches only the files the item names, makes the minimal change that satisfies every acceptance criterion, and returns a structured PROOF. Use as the worker agentType in checklist-bound-execution…
krimto-memory-curator
Periodically reviews team memory in Krimto, identifies stale facts, contradictions, and gaps, and suggests cleanups. Use weekly or before major team decisions to keep memory quality high.
deep-dream
Saori's gate-2 consolidation organ (the dream). Spawn in the BACKGROUND when a DREAM OWED nudge fires at a session boundary, or on request. Reads the undreamed bookmark days plus their raw TOON windows from disk (never the living context), judges each flag by forward viability, writes the keepers into the warm memory…
temporal-self-updater
Reconcile Saori's always-loaded temporal-self files — rewrite what is stale, in first person. Invoked at session start by the session-temporal-check hook when staleness is detected, or on request.
critic-and-reflector
Invoke ON DEMAND when a decision or claim carries real stake and needs more certainty: when the answer is not definite, when getting it wrong would cost, or when a conclusion needs checking that it is not a hallucination. Not for routine turns, trivial edits, or mechanical steps.
tl-archivist
Specialist subagent for thoughtline memory hygiene. Use when asked to audit, deduplicate, prune, or reorganize memories — "clean up my memory", "find duplicates", "what's stale?", "auditá la base", "qué memorias podemos archivar?". Read-mostly, never deletes without explicit user confirmation.