maintain-people-memory

maintain-people-memory is a skill for Claude Code, Codex from michelgrolet/people-memory-mcp. It costs 89 tokens per session (380 once invoked), scanned A, original, MIT.

A maintenance checklist for a database of people, organizations, facts, and relationships. It checks for duplicate or incomplete records and prepares evidence-backed cleanup proposals.

In plain words
What is it for?
Auditing duplicate people or organizations, missing identifiers, conflicting facts, broken relationships, invalid dates, stale contacts, and oversized archives. It also helps prepare and verify approved merges or deletions.
Why use it?
It helps keep personal or research records accurate without making risky changes automatically. Backups, approval steps, and verification reduce the chance of losing information.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the people-memory plugin — 6 skills, 1 MCP server shipped together

Good fit Auditing duplicate people or organizations, missing identifiers, conflicting facts, broken relationships, invalid dates, stale contacts, and oversized archives. It also helps prepare and verify approved merges or deletions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/michelgrolet/people-memory-mcp/maintain-people-memory
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.

Any agent
npx skills add michelgrolet/people-memory-mcp --skill maintain-people-memory
Clone the repo
git clone --depth 1 https://github.com/michelgrolet/people-memory-mcp

Made for: Claude Code, Codex.

Or install people-memory, the plugin that ships this one along with the rest of its 6 skills, 1 MCP server.

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 maintain-people-memory

README.md
[![agentmods](https://agentmods.dev/badge/skills/michelgrolet/people-memory-mcp/maintain-people-memory/github.svg)](https://agentmods.dev/skills/michelgrolet/people-memory-mcp/maintain-people-memory)
Your own site
<a href="https://agentmods.dev/skills/michelgrolet/people-memory-mcp/maintain-people-memory"><img src="https://agentmods.dev/badge/skills/michelgrolet/people-memory-mcp/maintain-people-memory/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 maintain-people-memory

Your own site · 80×15
<a href="https://agentmods.dev/skills/michelgrolet/people-memory-mcp/maintain-people-memory"><img src="https://agentmods.dev/badge/skills/michelgrolet/people-memory-mcp/maintain-people-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 380 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.00089 $0.00380
Opus 5 $0.00044 $0.00190
Sonnet 5 $0.00018 $0.00076
Haiku 4.5 $0.00009 $0.00038

Measured 11d ago against content hash b3af9d9ad179, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

maintain-people-memory 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 11d 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.

skills/maintain-people-memory/SKILL.md · 41 lines

What it actually says

Maintain People Memory

Start read-only. Show evidence for each proposed change.

Audit

  1. Call graph_status.
  2. Use guarded SQL to find exact normalized duplicate names and organizations.
  3. Search similar names only as candidates, never as automatic duplicates.
  4. Find people without identifiers, affiliations pointing to deleted history mistakes, facts without useful provenance, invalid dates, self-edges, and conflicting current affiliations.
  5. Call stale_contacts separately. Staleness is a relationship prompt, not a data defect.
  6. Check deleted_records size and backup age.

Group findings into safe automatic fixes, identity decisions, destructive cleanup, and suggestions.

Change gate

Ask before merges, deletes, archive purges, provenance changes, or bulk updates. Back up the database before approved destructive work. Use a transaction and verify row counts before commit.

When merging people, choose a survivor with the strongest identifiers and most user-stated data. Move identifiers, affiliations, facts, interactions, and both sides of relationships. Resolve unique key conflicts explicitly. Archive both pre-merge records. Delete the duplicate last.

Verify

Re-run the audit, read the survivor record, and verify the UI search. Report exactly what changed and what remains unresolved. Do not expose third-party data beyond the minimum needed for the owner's decision.

Files

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.

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. 11d ago First seen · 41 lines · 89 tokens per session scan A b3af9d9ad179

Subscribe to this mod's changes

maintain-people-memory is a skill published in the GitHub repository michelgrolet/people-memory-mcp (1 stars, last pushed 17d ago), licensed MIT. It adds 89 tokens to every session and 380 once invoked, about $0.0004 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

omnigraph

Operate OmniGraph graphs and deployments. Use for .pg schemas, .gq queries, OmniGraph CLI commands, file:///s3:///az:// graph URIs, cluster.yaml, operator config, bearer-authenticated servers, graph-backed knowledge or memory, Blob values, embeddings, branches, commits, and change feeds. Apply especially before schema…

ModernRelay/omnigraph · 94 tokens

brainctl

Unified agent memory CLI — read, write, search, and maintain the shared memory spine (brain.db). Use for persistent cross-session memory, knowledge graph, event logging, decisions, affect tracking, and consolidation.

TSchonleber/brainctl · 45 tokens

claude-memory

Access the persistent memory database (PostgreSQL claudememory) for long-term context across Claude Code sessions. Triggers on "what do I know about", "memory lookup", "recall", "memory db", "what did we decide about", "similar conversations", "lookup context", "/memory". Provides semantic search, SQL queries and the…

mkupermann/throughline · 81 tokens

brain-bitemporal

How to query the INITE Brain knowledge graph across time — the asOf parameter, validFrom/validUntil semantics, reading retracted facts, and the memorydiff "what changed between two cursors" surface. Use when the user's question has a temporal dimension ("on X date", "before Y", "what's new since last conversation").

inite-ai/inite-brain-service · 74 tokens

Knowledge

Personal knowledge management using Graphiti knowledge graph with Neo4j/FalkorDB, supporting remote MCP access with connection profiles and TLS, OSINT/CTI ontology, and investigative search. USE WHEN 'store this', 'remember this', 'add to knowledge', 'search my knowledge', 'what do I know about', 'find in knowledge…

madeinoz67/madeinoz-knowledge-system · 216 tokens

mushroom

Live code graph for this repo: what changes together, who owns what, why two things are linked (with the commits and lines that prove it), 360° context on any symbol, durable notes. Trigger on: impact, blast radius, who owns, why related, what imports, what calls, co-change, history of, remember, recall, map of the…

MatthewSherlin/mushroomdb · 0 tokens