Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rjmurillo/ai-agents/plugin install project-toolkitWrote 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/skills/rjmurillo/ai-agents/curating-memories)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/curating-memories"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/curating-memories/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/skills/rjmurillo/ai-agents/curating-memories"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/curating-memories.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.00091 | $0.01740 |
| Opus 5 | $0.00046 | $0.00870 |
| Sonnet 5 | $0.00018 | $0.00348 |
| Haiku 4.5 | $0.00009 | $0.00174 |
Grade A, and why
curating-memories 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 4d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curating Memories
Active curation keeps the knowledge base accurate. A memory that is fully resolved or historical but still reads as live guidance forces a fresh agent to read past archaeology to reach current truth, and outdated content pollutes every search that touches it.
This skill owns in-file supersession markers on .serena/memories/**. It never
merges or deletes Serena files and never edits Serena index files. Use
memory-consolidate for cross-file Serena merges, deletions, and index cleanup, and
memory-maintenance for health, token, and size checks.
Triggers
| Trigger Phrase | Operation |
|---|---|
how do I mark a memory obsolete |
Strike the obsolete content, add a dated banner |
how do I supersede a memory |
Apply the healthy-supersession shape below |
how do I clean up stale memories |
Run the sweep, then verify each proposal |
run the supersession sweep |
Scripts section below |
Scope
Serena memories are markdown files, not records in a store. There is no soft-delete, no obsolete flag, and no link table to write. Curation is an edit to the file's own text, and history survives because the file keeps it visible rather than because a backend hides it.
| In scope | Out of scope |
|---|---|
| Strike-through and dated banners inside one memory file | Merging two Serena memory files (memory-consolidate) |
| Collapsing a resolved investigation to a changelog footer | Deleting a memory file (memory-consolidate) |
| Adding a dated-snapshot banner to a point-in-time doc | Editing memory-index.md (memory-consolidate) |
| Running and verifying the supersession sweep | Store health, token, and size checks (memory-maintenance) |
When to Supersede
Supersede content when:
- Newer information contradicts it.
- A decision has been reversed or replaced.
- The code, script, workflow, or artifact it references no longer exists.
- The file records a resolved investigation but still reads as an open one.
- A dated point-in-time snapshot is framed as current state.
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.
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.
- 4d ago Changed · -106 lines · +2 tokens per session 8052678844b6
- 6d ago Changed · -5 lines 9dab6bdb2318
- 8d ago First seen · 256 lines · 89 tokens per session scan A 9ba83920573d
curating-memories is a skill published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 1,740 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
context-recovery
Recover missing conversation context after explicit compaction or truncation, or when the user explicitly asks to recover prior work. Use for requests such as "where were we before compaction?" when the current thread is insufficient. Do not trigger on a generic "continue" when the current thread already provides an…
ci-cd
A guide for designing automated build and delivery workflows with GitHub Actions. These workflows can run checks such as tests, code-quality scans, coverage checks, and builds when code is pushed or a pull request is opened.
context-search
A continuity workflow for finding context from earlier coding-agent sessions. It can inspect continuation notes and session records when a task refers to previous work.
abmind-runtime-operations
Inspect and maintain abmind memory, persona files, sleep, backups, encryption, and runtime health.
memory-search
Search persistent memory for facts, decisions, and past conversations.
context-pack
Compact the current conversation into a handoff document so a fresh agent can continue the work in the next session.