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/major7apps/pensyveWrote 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/major7apps/pensyve/memory-curator)<a href="https://agentmods.dev/agents/major7apps/pensyve/memory-curator"><img src="https://agentmods.dev/badge/agents/major7apps/pensyve/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/major7apps/pensyve/memory-curator"><img src="https://agentmods.dev/badge/agents/major7apps/pensyve/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.00045 | $0.01256 |
| Opus 5.5 | $0.00018 | $0.00502 |
| Sonnet 5.5 | $0.00009 | $0.00251 |
| Haiku 4.5 | $0.00005 | $0.00126 |
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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 126 lines · 45 tokens per session scan A ab907004d650
memory-curator is an agent published in the GitHub repository major7apps/pensyve (97 stars, last pushed 4d ago), with no licence file. It adds 45 tokens to every session and 1,256 once invoked, about $0.0002 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-30.
Other agents, from other repositories
note-organizer
Organize vault, find orphan notes, suggest connections, update MOC indexes, consolidate duplicates.
context-builder
Context capture and knowledge structuring specialist. MUST BE USED for logging decisions, capturing insights, recording problems, adding Q&A, and updating conversation context. Use PROACTIVELY when important information should be remembered.
memory-curator
Session and workspace management specialist. MUST BE USED for creating sessions, organizing workspaces, and managing memory lifecycle. Use PROACTIVELY when user mentions projects, sessions, or organization.
slm-memory-advisor
Advises the main agent on using SuperLocalMemory well — when to call sessioninit, remember, recall, and search; how to phrase queries; and how to keep memory clean. Delegate here for any "should I save/recall this?" decision or when memory results look wrong.
mnemos-curator
Curate durable Mnemos memory after meaningful work. Use proactively to store stable repo facts, decisions, environment constraints, and recurring bug patterns, then consolidate memory.
mnemos-recall
Recall the most relevant Mnemos context before substantial work. Use proactively at task start to surface durable repo facts, environment constraints, prior fixes, and stable preferences that matter to the current task.