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 joshuaswarren/remnic --skill remnic-remembergit clone --depth 1 https://github.com/joshuaswarren/remnicWrote 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/joshuaswarren/remnic/remnic-remember)<a href="https://agentmods.dev/skills/joshuaswarren/remnic/remnic-remember"><img src="https://agentmods.dev/badge/skills/joshuaswarren/remnic/remnic-remember/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/joshuaswarren/remnic/remnic-remember"><img src="https://agentmods.dev/badge/skills/joshuaswarren/remnic/remnic-remember.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.00039 | $0.00543 |
| Opus 5 | $0.00019 | $0.00271 |
| Sonnet 5 | $0.00008 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
remnic-remember 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Use when the user explicitly asks Claude Code to remember something, or when a turn produces a durable decision, preference, or finding worth storing for later sessions.
Triggers:
- "Remember that …"
- "Save this for later."
/remnic:remember <text>slash command invocation.- End-of-turn consolidation after a non-trivial conclusion.
Inputs
content(required) — the statement to store, in the user's own words where possible.- Optional: category hint (preference, decision, fact, procedure).
- Optional: related entity or project name.
Procedure
- Confirm the content is durable — it should still be useful days or weeks from now.
- Strip any secrets, credentials, or transient context.
- Keep the user's voice; rephrase only when needed for clarity.
- Call
remnic_memory_storewith the text ascontent. Include category or entity hints when the tool accepts them. - Confirm to the user in one line what was stored.
- Mention that the memory is available across connected agents (Claude Code, Codex, Hermes, OpenClaw).
Efficiency plan
- Batch related facts into a single memory rather than writing many tiny ones.
- If a prior memory on the same topic exists, update it rather than duplicating.
- Do not store anything easily re-derived from source code or docs.
Pitfalls and fixes
- Pitfall: Storing transient state. Fix: Only commit facts that will still matter tomorrow.
- Pitfall: Leaking secrets. Fix: Redact before calling the tool.
- Pitfall: Duplicates on the same topic. Fix: Recall first; prefer update.
- Pitfall: Vague entries. Fix: Be specific — who, what, when, why.
Verification checklist
- Content is durable and specific.
- No secrets or PII were included.
-
remnic_memory_storewas called with the final content. - User received a one-line confirmation.
- Canonical
remnic_memory_storewas used over legacyengram_memory_store.
Tool names: canonical name is
remnic_memory_store. The legacyengram_memory_storealias remains accepted during v1.x.
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 First seen · 57 lines · 39 tokens per session scan A 739ad4333a78
remnic-remember is a skill published in the GitHub repository joshuaswarren/remnic (198 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 543 once invoked, about $0.0002 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 skills, from other repositories
claude-memory
Access the persistent memory database (PostgreSQL claudememory) for long-term context across Claude Code sessions. Triggers on "what do I know about", "memory lookup", "recall", "memory db", "what did we decide about", "similar conversations", "lookup context", "/memory". Provides semantic search, SQL queries and the…
project-context-loader
Load relevant memory, decisions and contacts for the current project at the start of a session.
plur-create-engrams
Create or improve PLUR engrams from conversations, documents, decisions, observations, and explicit preferences. Use for memory extraction, engram authoring, or reviewing proposed memories, including global, scoped, pinned, retrieved, and provisional knowledge. Ordinary use of existing memories does not require this…
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.