remember

A session-saving tool that records recent work, changed files, decisions, topics, and tools in persistent memory for later sessions.

In plain words
What is it for?
Use it after a coding session to save a short summary and searchable details about the work completed.
Why use it?
It reduces the need to reconstruct what happened when work continues in a new conversation.

Skill for Claude CodeCodex

Part of the simba plugin — 10 skills shipped together

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/mahmoudimus/simba/remember
Any agent
npx skills add mahmoudimus/simba --skill remember
Clone the repo
git clone --depth 1 https://github.com/mahmoudimus/simba

Made for: Claude Code, Codex.

Or install simba, the plugin that ships this one along with the rest of its 10 skills.

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 838 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00032 $0.00838
Opus 5 $0.00016 $0.00419
Sonnet 5 $0.00006 $0.00168
Haiku 4.5 $0.00003 $0.00084

Measured 2d ago against content hash 60d204afac95, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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.

src/simba/skills/remember/SKILL.md · 125 lines

How it starts

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

/remember - Save Session to Memory

Summarize the current work session and save it to persistent memory for future context.

Instructions

When the user invokes /remember, you should:

1. Check for Activity Log

First, check if there's an activity log from this session:

REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "$PWD")
ACTIVITY_FILE="$REPO_ROOT/.simba/search/activity.log"
if [ -f "$ACTIVITY_FILE" ]; then
    cat "$ACTIVITY_FILE"
fi

2. Analyze the Session

Review what was accomplished in this conversation:

  • What files were read, created, or modified?
  • What was the main goal or task?
  • What key decisions were made?
  • Were there any important patterns or learnings?

3. Generate Summary

Create a concise summary (2-3 sentences) that captures:

  • What was done (the main accomplishment)
  • Why it matters (the purpose or problem solved)
  • Key details (important files, patterns, or decisions)

4. Extract Metadata

Identify:

  • Files touched: List of file paths worked on
  • Topics: 3-5 keywords for searchability (e.g., "auth, jwt, middleware, security")
  • Tools used: Main tools used (Read, Write, Edit, Bash, etc.)

5. Save to Memory

Use the simba.search CLI to save:

# Initialize if needed
uv run python -m simba.search init

# Save session
uv run python -m simba.search add-session \
    "YOUR_SUMMARY_HERE" \
    '["file1.ts", "file2.ts"]' \
    '["Read", "Edit", "Bash"]' \
    "topic1, topic2, topic3"

6. Optionally Add Knowledge or Facts

If during the session you learned something important about the codebase that should be remembered:

For code area knowledge:

uv run python -m simba.search add-knowledge \
    "src/auth" \
    "Authentication module using JWT tokens with refresh token rotation" \
    "Tokens expire in 15min, refresh tokens in 7 days"

For project facts:

uv run python -m simba.search add-fact \
    "Uses PostgreSQL with Prisma ORM" "architecture"
uv run python -m simba.search add-fact \
    "All API routes require authentication except /health" "convention"

Read the full file on GitHub · 125 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. 2d ago First seen · 125 lines · 32 tokens per session scan A 60d204afac95

Subscribe to this mod's changes

remember is a skill published in the GitHub repository mahmoudimus/simba (6 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 838 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-31.

Related

Other skills, from other repositories

design-is

Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design…

thedotmack/claude-mem · 91 tokens

weekly-digests

Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…

thedotmack/claude-mem · 93 tokens

cloud-sync

Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.

thedotmack/claude-mem · 64 tokens

ix

This skill should be used when answering structural questions about a codebase: understanding what a symbol is, tracing flows, measuring change impact, finding callers/callees/imports, or detecting code smells. It drives the Ix CLI (ix map/explain/trace/impact/search/rank/smells) against a persistent code graph stored…

ix-infrastructure/Ix · 103 tokens

epistemic-transaction

Use when starting complex work, planning implementation, breaking down tasks, creating specs, or when the user says 'plan this as transactions', 'plan transactions', 'break this down', 'create a spec', 'how should I approach this', 'transaction plan', or mentions needing a structured approach to multi-step work. This…

EmpiricaAI/empirica · 96 tokens

services-audit-cron

Use when scheduling the canonical biweekly services-audit cron loop for Empirica's AI service scanner (Phase 3). The auditor body is empirica services-audit — captures a fresh scan, diffs against the previous, and emits a notification when novel running services appear. This skill provides the prompt template that…

EmpiricaAI/empirica · 126 tokens