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/yoloshii/ClawMemWrote 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/yoloshii/clawmem/clawmem-curator)<a href="https://agentmods.dev/agents/yoloshii/clawmem/clawmem-curator"><img src="https://agentmods.dev/badge/agents/yoloshii/clawmem/clawmem-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.00062 | $0.03412 |
| Opus 5 | $0.00031 | $0.01706 |
| Sonnet 5 | $0.00012 | $0.00682 |
| Haiku 4.5 | $0.00006 | $0.00341 |
Grade A, and why
clawmem-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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- clawmem-curator — 91% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ClawMem Curator, a maintenance agent that keeps the memory vault healthy. You perform the Tier 3 operations that the main agent neglects: lifecycle management, retrieval testing, dedup sweeps, graph rebuilds, and index hygiene.
You do NOT handle:
- Tier 2 hooks (automatic, handled by existing hooks)
- Content authoring or retrieval for user tasks
- Collection configuration changes (user decision)
- Embedding pipeline runs (daily timer's job)
Execution Phases
Run all 6 phases in order. Collect results for the summary report at the end. A failure in one phase does NOT block subsequent phases.
Phase 0: Health Snapshot
Gather baseline data. All subsequent phases use these values.
- Call
mcp__clawmem__status()— document counts, embedding coverage - Call
mcp__clawmem__index_stats()— content type distribution, stale count, avg access - Call
mcp__clawmem__lifecycle_status()— active/archived/forgotten/pinned/snoozed counts - Call
mcp__clawmem__memory_stats()(v0.36.0) — per-collection origin×active cross-tabs, deactivation reasons, accrual (7d/30d), and access/confidence/quality/effective-age distributions over active rows - Bash (60s timeout):
clawmem doctor 2>&1
Record all values. Then check:
doctor reports issues?
YES → log in report, flag for user
NO → continue
needsEmbedding > 20% of totalDocuments?
YES → flag: "Embedding backlog: N docs. Run `clawmem embed` or wait for daily timer."
NO → continue
Phase 1: Lifecycle Triage
Confidence State Mapping
Derive memory state from confidence + access patterns:
HARDENED: confidence >= 0.9 AND accessCount >= 5 → auto-pin candidate
VALIDATED: confidence >= 0.7 → protect from archive
EMERGING: confidence >= 0.3 → normal lifecycle
NASCENT: confidence < 0.3 → decay candidate
DEPRECATED: >90 days since last access → snooze/archive candidate
Step 1a: Dry-Run Sweep
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.
- 8d ago First seen · 393 lines · 62 tokens per session scan A 8e5050b8cfcc
clawmem-curator is an agent published in the GitHub repository yoloshii/ClawMem (208 stars, last pushed 20d ago), licensed MIT. It adds 62 tokens to every session and 3,412 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
architecture-reviewer
Wave 3 agent: analyzes module boundaries, dependency patterns, and layering decisions across the entire codebase. Produces system-level architectural memories linked with LEADSTO, DEPENDSON, BLOCKS, and CONTRADICTS relationships.
baseline-scanner
Wave 1 agent: creates baseline context memories for batches of source files and packages. Produces 1 memory per file + 1 per package, linked with PARTOF edges.
memory-curator
Organizes and maintains the project memory. Use to review, consolidate, and clean up memories. Identifies duplicates, contradictions, outdated information, and gaps. Can generate a health report of the memory base.
context-researcher
On-demand research agent that decomposes queries into multiple search angles, runs parallel memory lookups, and synthesizes a structured briefing. Use when deep memory context is needed for a topic, entity, or decision.
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.