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 skills/remember-md/remember/processnpx skills add remember-md/remember --skill processgit clone --depth 1 https://github.com/remember-md/rememberWhat 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.00014 | $0.02149 |
| Opus 5 | $0.00007 | $0.01074 |
| Sonnet 5 | $0.00003 | $0.00430 |
| Haiku 4.5 | $0.00001 | $0.00215 |
Grade A, and why
remember:process 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 yesterday.
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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/remember:process — Process Sessions into Second Brain
Reads unprocessed Claude Code transcripts and routes valuable content into your Second Brain using a knowledge-aware pipeline.
Only use Bash for running Node.js scripts. Use Read/Write/Edit/Glob/Grep for all file operations.
Core Principles
- Chronology:
session_date < file_last_modified→ OLD SESSION (append only, no replace, no frontmatter update). Otherwise → normal update. - Knowledge Index: Built in Step 1. Use throughout to resolve entities, link with
[[wikilinks]], prevent duplicates. - REMEMBER.md overrides: User instructions take precedence over default routing.
Step 1: Build Knowledge Index
- Read
$REMEMBER_BRAIN_PATHenv var (fallback~/remember). Call this{brain}. - If missing → tell user to run
/remember:initand stop. - Run:
node ${CLAUDE_PLUGIN_ROOT}/scripts/build-index.js - Read output — this is your map of everything that exists.
Step 1b: Load User Instructions
Read REMEMBER.md (cascading): {brain}/REMEMBER.md (global) + {project_root}/REMEMBER.md (project, if exists). These override default routing, capture rules, templates, and custom types.
Step 1c: Batch Chronology Map
Run once to get last-modified dates for all brain files:
cd {brain} && git log --format="%ai" --name-only --diff-filter=ACMR HEAD | paste - - | sort -k2 -u
Parse into a lookup map: file_path → last_modified_date. Use this in Step 4c instead of per-file git log calls.
Step 2: Find Unprocessed Sessions
node ${CLAUDE_PLUGIN_ROOT}/scripts/extract.js --unprocessed
Optional filters: --project <name>, --source openclaw|claude-code.
Show the list. Ask user which to process: All, specific sessions by number, or Skip.
Step 3: Extract Each Session
node ${CLAUDE_PLUGIN_ROOT}/scripts/extract.js <file_path>
Use the **Session date (use for journal/tasks):** line as SESSION_DATE for everything. Never use today's date.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 190 lines · 14 tokens per session scan A 97b5c2e27011
remember:process is a skill published in the GitHub repository remember-md/remember (58 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 2,149 once invoked, about $0.0001 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
designing-commands
Use when someone wants to add their own slash command to this vault — most often /query (ask the wiki a question), but also /lint, /gaps, /weekly, or anything else. Guides them through the design decisions that make it theirs, then writes the command file. Trigger on "help me write a command", "build my query…
pos-verify
Use this immediately after files are created, edited, moved, deleted, or materially rewritten inside PersonalOS. Verifies that new truth was routed to the correct owner, written in the correct file shape, and still follows POS conventions. Do NOT use for whole-vault deep audits; use system-health-check.
skillify
Use this when {{username}} asks to skillify a repeated workflow, determine whether it deserves a reusable PersonalOS skill, or harden an existing workflow into a tested resolver-reachable capability. Do NOT use for one-off notes, ordinary execution, or already-specified skill authoring; use write-skill.
write-skill
Use this when the user wants to create a new shared PersonalOS skill under skills/ or revise a specified PersonalOS skill and the scope is already clear. Do NOT use for raw workflow capture or deciding whether work should become a skill; use skillify first. Do NOT use for repo-local or agent-local skills unless…
priority-dashboard
Use this to rebuild, inspect, or temporarily steer {{username}}'s current PersonalOS priority dashboard from canonical Actions, Attention Triggers, and owner context. Do NOT use it to create, complete, or independently manage tasks; use task-manager for Action and Trigger lifecycle changes.
lint-brain
Run health checks over the brain vault - find orphan notes, broken wikilinks, missing frontmatter, stale projects, and missing cross-links. Use when asked to "lint the brain", "health check", "vault hygiene", or "/lint-brain".