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 remember-md/remember --skill statusgit clone --depth 1 https://github.com/remember-md/rememberWrote 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/remember-md/remember/status)<a href="https://agentmods.dev/skills/remember-md/remember/status"><img src="https://agentmods.dev/badge/skills/remember-md/remember/status/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/remember-md/remember/status"><img src="https://agentmods.dev/badge/skills/remember-md/remember/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00011 | $0.01141 |
| Opus 5.5 | $0.00004 | $0.00456 |
| Sonnet 5.5 | $0.00002 | $0.00228 |
| Haiku 4.5 | $0.00001 | $0.00114 |
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 1mo 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.
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. 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 rungit -C {brain_path} status --porcelain | wc -land 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.
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.
- 1mo ago First seen · 134 lines · 11 tokens per session scan C e75eff1c3c2e
remember:status is a skill published in the GitHub repository remember-md/remember (63 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 1,141 once invoked, about $0.0000 per session on Opus 5.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.
Other skills, from other repositories
log
Use this when a PersonalOS work session, chat outcome, personal reflection, or provided source should be persisted into the modular Daily context and any already-owned canonical files. Do NOT use for single-call processing, single-source knowledge ingestion, Gmail/WhatsApp propagation, or Lexware booking.
analyse-call
Use this when a local call transcript or meeting note should be analyzed into traceable PersonalOS context. Preserves the source, separates evidence from interpretation, updates only proven owner truth, routes confirmed commitments through task-manager, and never sends messages or triggers external actions without…
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".
ingest-article
Ingest an article from a URL or raw text into the brain vault. Extracts key knowledge, determines placement, creates or updates notes, and links to relevant projects. Use when the user shares a URL or text and wants to absorb it into their knowledge base.
wrap-session-up
End-of-session review for a Claude Code conversation. Replays what was discussed, checks for open action items, documents relevant outcomes in the brain vault, and creates Todoist tasks for anything untracked. Use at the end of a work session to ensure nothing falls through the cracks.
kickoff
Guided first-run setup for a forked brain-starter vault. Walks through identity, first project, semantic search, integrations, indexes, and the first commit - verifying each phase before moving on. Use when the user has just forked or cloned brain-starter, says "set up my brain", "I just forked brain-starter", or runs…