remember:status

A command for showing statistics and recent activity for the Remember Second Brain, a file-based personal knowledge store.

In plain words
What is it for?
Use it with `/remember:status` to view file counts, recent activity, and brain-health information using the required built-in file tools.
Why use it?
It provides a quick view of whether the stored knowledge base exists, is active, and appears healthy.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/remember-md/remember/status
Any agent
npx skills add remember-md/remember --skill status
Clone the repo
git clone --depth 1 https://github.com/remember-md/remember

Made for: Claude Code, Codex.

Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,141 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.01141
Opus 5 $0.00005 $0.00571
Sonnet 5 $0.00002 $0.00228
Haiku 4.5 $0.00001 $0.00114

Measured yesterday against content hash e75eff1c3c2e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

remember:status scanned grade C 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.

Tells the agent never to refusehighAnti-refusal

Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.

This is non-blocking — never refuse to show stats just because backup is missing.
skills/status/SKILL.md · 134 lines

How it starts

The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/remember:status - Remember Status

Displays brain statistics: file counts, recent activity, and brain health.

Usage

/remember:status

⚠️ MANDATORY: Use Built-in Tools Only (NO Bash!)

NEVER use Bash commands for brain operations. Use Claude Code's built-in tools which are auto-approved and require zero permission prompts:

Operation ✅ Use This ❌ NOT This
List files LS tool bash ls
Find files Glob tool bash find
Search content Grep tool bash grep
Read files Read tool bash cat
Write/create files Write tool bash echo > / bash tee
Count files Glob tool + count results bash wc
Check env vars Already available as $REMEMBER_BRAIN_PATH bash echo $VAR

For complex operations (stats, counting, multi-step), use a subagent (Task tool) that uses the same built-in tools.

Why: additionalDirectories auto-approves LS/Glob/Grep/Read/Write. Bash always prompts.

Steps

1. Resolve Brain Path

Read $REMEMBER_BRAIN_PATH env var, fallback ~/remember. Use this as {brain_path}. If brain path doesn't exist → tell user to run /remember:init.

2. Show Brain Statistics

See "What to show" below for the full output template.

3. Show Recent Activity

List recently modified files (last 7 days) across People/, Projects/, Journal/, Notes/.

4. Show Persona Summary

Read {brain_path}/Persona.md and show a brief summary of captured patterns.

5. Backup health check

Check if {brain_path}/.git/ exists (use LS tool on {brain_path}/.git):

  • Exists → show Backup: ✅ git-tracked. If you want to be helpful, also run git -C {brain_path} status --porcelain | wc -l and surface uncommitted-file count if > 0 (e.g. Backup: ✅ git-tracked · 12 uncommitted files — consider committing).

  • Missing → show a warning block at the end of the output:

    ⚠️  Backup: NOT git-tracked
    
    Your brain lives at {brain_path} but has no git history. A single bad
    capture or accidental delete could lose months of work.
    
    Recommended:
      cd {brain_path}
      git init
      git add .
      git commit -m "initial brain snapshot"
    
    (Optional) push to a private GitHub repo for off-machine backup.
    

Read the full file on GitHub · 134 lines

Changes

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.

  1. yesterday First seen · 134 lines · 11 tokens per session scan C e75eff1c3c2e

Subscribe to this mod's changes

remember:status is a skill published in the GitHub repository remember-md/remember (58 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 1,141 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

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…

briannaworkman/commonplace · 108 tokens

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.

vincentmumme/personalos-boilerplate · 65 tokens

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.

vincentmumme/personalos-boilerplate · 66 tokens

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…

vincentmumme/personalos-boilerplate · 78 tokens

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.

vincentmumme/personalos-boilerplate · 60 tokens

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".

michaeljauk/brain-starter · 56 tokens