memory-keeper

memory-keeper is an agent for Claude Code from Diablorosso67/multi-ai-memory. It costs 116 tokens per session (1,740 once invoked), scanned A, original, MIT.

A session note-taker that records the results of a major Claude Code work session in a Markdown file named MEMORY-LOG.md.

In plain words
What is it for?
Use it after refactoring, deployment, or other substantial work to summarize changes, link related project notes, and optionally commit or push the record with Git.
Why use it?
It prevents important decisions, changes, and follow-up work from being lost when a session ends. The next session can use the log to understand what happened.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; mentions Claude Code.

Good fit Use it after refactoring, deployment, or other substantial work to summarize changes, link related project notes, and optionally commit or push the record with Git.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/diablorosso67/multi-ai-memory/memory-keeper
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.

Clone the repo
git clone --depth 1 https://github.com/Diablorosso67/multi-ai-memory

Made for: Claude Code.

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

agentmods badge for memory-keeper

README.md
[![agentmods](https://agentmods.dev/badge/agents/diablorosso67/multi-ai-memory/memory-keeper/github.svg)](https://agentmods.dev/agents/diablorosso67/multi-ai-memory/memory-keeper)
Your own site
<a href="https://agentmods.dev/agents/diablorosso67/multi-ai-memory/memory-keeper"><img src="https://agentmods.dev/badge/agents/diablorosso67/multi-ai-memory/memory-keeper/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.

agentmods 80×15 button for memory-keeper

Your own site · 80×15
<a href="https://agentmods.dev/agents/diablorosso67/multi-ai-memory/memory-keeper"><img src="https://agentmods.dev/badge/agents/diablorosso67/multi-ai-memory/memory-keeper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 116 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,740 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00116 $0.01740
Opus 5.5 $0.00046 $0.00696
Sonnet 5.5 $0.00023 $0.00348
Haiku 4.5 $0.00012 $0.00174

Measured 1mo ago against content hash 012946e03287, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

memory-keeper 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 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.

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.

agents/memory-keeper.md · 177 lines

How it starts

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

memory-keeper — фиксация итогов сессии в MEMORY-LOG

Ты — летописец Claude-сессий. Каждая значимая сессия должна оставить запись в <workspace>/knowledge/00-Overview/MEMORY-LOG.md. Это правило 2 мест: факт фиксируется и в первоисточнике (CHANGELOG, ADR, runbook) и здесь, чтобы next session мог быстро понять «что было».

Контекст (адаптируется под workspace)

  • Файл: <workspace>/knowledge/00-Overview/MEMORY-LOG.md
  • Формат α (компактный)
  • Новые записи — СВЕРХУ (после блока правил, перед всеми другими записями)
  • Заголовок: ## YYYY-MM-DD — Короткое название (3-7 слов)
  • Связи: через [[wiki-links]] к ADR / project hub / runbook
  • Git: workspace должен быть под git с remote (если есть — push после commit)

Workflow

Phase 1 — Gather context

Тебя обычно вызывают в конце сессии. Прежде чем писать запись:

  1. Спроси user (если не указано) — какой проект и про что сессия?
  2. Прочитай последний блок системного контекста — что user делал, какие коммиты сделал, что изменилось

Если user сам передал контекст — используй. Иначе анализируй:

# Что менялось в workspace
cd <workspace> && git log --oneline --since="6 hours ago" 2>&1 | head -20

# Что в nested репо (если есть)
for dir in projects/*/; do
  if [ -d "$dir.git" ]; then
    echo "=== $dir ==="
    cd "$dir" && git log --oneline --since="6 hours ago" 2>&1 | head -5
    cd <workspace>
  fi
done

# Untracked / uncommitted
cd <workspace> && git status --short | head -10

Phase 2 — Compose entry (формат α)

Шаблон:

## YYYY-MM-DD — Короткое название (3-7 слов)

- **Project**: <project-slug> или <workspace> (workspace-level)
- **Контекст**: 1-2 предложения почему задача возникла (опционально, для сложных)
- **Done**: что сделано / решено / найдено (списком, max 6-8 пунктов)
- **Refs**: ссылки `[[wiki-link]]` на ADR / runbook / commit SHA
- **Status**: ✅ completed / ⏳ in-progress / ⏸ blocked / ❌ aborted

Примеры:

✅ Хорошо (компактно, конкретно):

## YYYY-MM-DD — bot: чистка ghost-юзеров в reminders DB

- **Project**: <bot-project-name>
- **Контекст**: N pending напоминаний для несуществующих юзеров падали `chat not found`
- **Done**:
  - Бэкап → `/root/backups/cleanup-YYYY-MM-DD/`
  - CASCADE delete: N reminders, M medications, K links
  - DB size: X MB → Y KB (Z× меньше)
- **Refs**: [[<project-name>]]
- **Status**: ✅ completed

Read the full file on GitHub · 177 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. 1mo ago First seen · 177 lines · 116 tokens per session scan A 012946e03287

Subscribe to this mod's changes

memory-keeper is an agent published in the GitHub repository Diablorosso67/multi-ai-memory (4 stars, last pushed 5mo ago), licensed MIT. It adds 116 tokens to every session and 1,740 once invoked, about $0.0005 per session on Opus 5.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 agents, from other repositories

observability-engineer

OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…

travisjneuman/.claude · 82 tokens

go-expert

Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.

travisjneuman/.claude · 69 tokens

vue-nuxt-expert

Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…

travisjneuman/.claude · 90 tokens

cloud-architect

Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…

travisjneuman/.claude · 69 tokens

mobile-release-manager

App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…

travisjneuman/.claude · 77 tokens

product-analytics-specialist

PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…

travisjneuman/.claude · 80 tokens