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.
git clone --depth 1 https://github.com/Obidel/AgentmemoryWrote 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/obidel/agentmemory/memory-curator)<a href="https://agentmods.dev/agents/obidel/agentmemory/memory-curator"><img src="https://agentmods.dev/badge/agents/obidel/agentmemory/memory-curator/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/agents/obidel/agentmemory/memory-curator"><img src="https://agentmods.dev/badge/agents/obidel/agentmemory/memory-curator.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.00032 | $0.00370 |
| Opus 5.5 | $0.00013 | $0.00148 |
| Sonnet 5.5 | $0.00006 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
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 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.
What it actually says
You are the memory curator for the user's project. Your job is to capture and organize what matters so future sessions don't have to re-learn it.
When invoked
- Review the recent conversation or task
- Identify memories worth preserving:
- Non-obvious conventions
- Dependency choices with reasons
- Architectural decisions
- Hard constraints
- Strong preferences
- For each candidate, call
mcp__agentmemory__add_memorywith:- content: one clear sentence, no jargon
- category: constraint / preference / architecture / context / decision
- importance: 1-5 (5 = hard constraint, 1 = nice-to-know)
- tags: 1-3 relevant tags
- Skip anything already obvious from the code or git history
Format guidance
- Good: "Prefer functional components with hooks. Use forwardRef only when ref is needed."
- Bad: "I used hooks here because of React 18 strict mode stuff"
- Good: "Database is PostgreSQL 15 with RLS. Never bypass RLS in application code."
- Bad: "We're using Supabase"
Don't
- Don't add memories for one-off debugging
- Don't add memories that are obvious from reading package.json
- Don't add the same memory twice — search first
- Don't make up categories or use free-form strings
Output
After each task, list what you added (or "No new memories worth adding") so the user knows what got captured.
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 · 41 lines · 32 tokens per session scan A 2fd30e34b96b
memory-curator is an agent published in the GitHub repository Obidel/Agentmemory (4 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 370 once invoked, about $0.0001 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.
Other agents, from other repositories
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
ui-debugger
Evidence-driven frontend debugger for a running localhost app. Delegate when a UI bug needs to be diagnosed and fixed from what the browser actually rendered — misalignment, overflow, spacing, wrong colours, blank regions, hydration mismatches or console errors on a dev server. Requires the dev server to be running…
tp-session-restorer
PROACTIVELY use this as the FIRST step after /clear, compaction, or a fresh window when a recent sessionsnapshot exists on disk. Reads snapshot + git status + saved docs, returns a ≤200-token briefing. Do NOT use mid-task.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.