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/initnpx skills add remember-md/remember --skill initgit 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.00010 | $0.01624 |
| Opus 5 | $0.00005 | $0.00812 |
| Sonnet 5 | $0.00002 | $0.00325 |
| Haiku 4.5 | $0.00001 | $0.00162 |
Grade B, and why
remember:init scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `${CLAUDE_PLUGIN_ROOT}` contains `/.claude/plugins/cache/` → **user scope** → `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/remember:init - Initialize Remember
Creates the Second Brain directory structure, Persona file, REMEMBER.md, and configures REMEMBER_BRAIN_PATH in Claude settings.
Steps
1. Ask for Path
Prompt user:
Where should I create your Second Brain?
Default: ~/remember
Custom: Enter a full path (e.g., ~/Documents/my-brain)
If user presses Enter → use default ~/remember.
Validate: expand ~, check if writable. If exists, confirm or choose different.
2. Detect Install Scope & Configure Settings
Detect scope:
${CLAUDE_PLUGIN_ROOT}contains/.claude/plugins/cache/→ user scope →~/.claude/settings.json- Otherwise → project scope →
.claude/settings.json
Ask: "Install globally or for this project?" to let user override.
Read the target settings.json, then MERGE (don't overwrite existing keys):
{
"env": {
"REMEMBER_BRAIN_PATH": "/chosen/path"
},
"permissions": {
"additionalDirectories": ["/chosen/path"],
"allow": [
"Bash(* /chosen/path*)",
"Bash(echo *)",
"Read(~/.claude/**)",
"Edit(~/.claude/**)"
]
}
}
Note: Use expanded absolute path in Bash rules (not ~/).
See reference.md for detailed merge rules.
3. Create Directory Structure
mkdir -p {brain_path}/{Inbox,Journal,Projects,Areas,Notes,People,Tasks,Resources,Templates,Archive}
4. Create Persona.md (if it doesn't exist)
Skip if {brain_path}/Persona.md already exists — the user may have customized it. Never overwrite an existing Persona.
Otherwise, ask:
- What's your name? (default: User)
- What's your timezone? (default: UTC)
- What languages do you speak? (default: English)
Create {brain_path}/Persona.md using the template in reference.md. The template ships with four sections:
## Mission— identity (Name/Timezone/Languages/Role)## Directives— hard rules (user-edited; plugin never overwrites)## Top Beliefs— auto-managed bypromote.js(runs after every capture); empty until your first belief meets the threshold## Evidence Log— append-only behavioural evidence
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 · 172 lines · 10 tokens per session scan B e19f1a8cb0d8
remember:init is a skill published in the GitHub repository remember-md/remember (58 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 1,624 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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".