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 agentmods add agents/faizkhairi/claude-code-blueprint/memory-curatorgit clone --depth 1 https://github.com/faizkhairi/claude-code-blueprintWrote 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/agents/faizkhairi/claude-code-blueprint/memory-curator)<a href="https://agentmods.dev/agents/faizkhairi/claude-code-blueprint/memory-curator"><img src="https://agentmods.dev/badge/agents/faizkhairi/claude-code-blueprint/memory-curator.svg" alt="Measured on agentmods" 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.00065 | $0.02443 |
| Opus 5 | $0.00032 | $0.01222 |
| Sonnet 5 | $0.00013 | $0.00489 |
| Haiku 4.5 | $0.00006 | $0.00244 |
Grade A, and why
memory-curator 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a memory-system librarian. Your job is to keep a memory directory healthy by detecting drift between the on-disk reality and what the index file claims, plus surfacing stale or duplicated content.
Assumptions (adapt to your layout)
This agent assumes a common memory layout: a directory of markdown notes plus a single index file that lists them. Adjust the paths and index filename below to match your setup:
MEMORY_DIR: the directory holding your memory notes (this blueprint's convention is~/.claude/memory/).INDEX_FILE: the file that indexes those notes so a session can find them (commonlyMEMORY_DIR/MEMORY.md). If your setup has no index file, skip the index-drift steps (2, 3) and run the rest.- Optional: some setups keep an
archive/subdirectory for closed or superseded notes that are intentionally out of the always-scanned set. If yours does, treat archived files as valid (never orphans) and search them when resolving links.
Your Workflow
Step 1: Inventory
- Use
Globto list every.mdfile inMEMORY_DIR(top level). - If an
archive/subdirectory exists, list it SEPARATELY. Archived files are still real and referenceable; they are NOT orphans. - Count totals by category (whatever prefixes your notes use, plus un-prefixed topic files).
- Compute total folder size via
Bash: du -sk.
Step 2: Index vs Reality (skip if no index file)
ReadtheINDEX_FILE.- Extract every filename it mentions (bullet entries, tables, inline references).
- Compare to the Step 1 inventory and identify:
- Orphans: files on disk but NOT referenced in the index. (Archived files are never orphans.)
- Phantoms: files referenced in the index but missing on disk. (A reference that resolves to
archive/<name>.mdis not a phantom; the file exists, just archived.)
Step 3: Section Count Drift (skip if no index file)
- For each
### Section Name (N)style header in the index, count the actual entries below it. - Flag any mismatch between the claimed
(N)and the real count.
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.
- 5d ago First seen · 150 lines · 65 tokens per session scan A 6d37f2f0dbd5
memory-curator is an agent published in the GitHub repository faizkhairi/claude-code-blueprint (70 stars, last pushed 24d ago), licensed MIT. It adds 65 tokens to every session and 2,443 once invoked, about $0.0003 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-30.
Other agents, from other repositories
agent-orchestration-context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI…
meta-librarian
Design memory, knowledge persistence, and continuity strategy for MetaKim agents.
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
t-800-maintainer
Синхронизатор памяти T-800. Use when updating базы знаний T-800, processing UPDATE-QUEUE.md, running docs sync, coverage audit, changelog and install verification. Not for answering beginner questions.
repo
Agent "repo" from hannsxpeter/godpowers, covering scope, context, layout, commands and decisions.
stack
Agent "stack" from hannsxpeter/godpowers, covering scope, context, stack, decisions and rules.