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 skills add DollarDill/beads-superpowers --skill memory-curatorgit clone --depth 1 https://github.com/DollarDill/beads-superpowersWrote 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/dollardill/beads-superpowers/memory-curator)<a href="https://agentmods.dev/skills/dollardill/beads-superpowers/memory-curator"><img src="https://agentmods.dev/badge/skills/dollardill/beads-superpowers/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/skills/dollardill/beads-superpowers/memory-curator"><img src="https://agentmods.dev/badge/skills/dollardill/beads-superpowers/memory-curator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.02604 |
| Opus 5 | $0.00026 | $0.01302 |
| Sonnet 5 | $0.00010 | $0.00521 |
| Haiku 4.5 | $0.00005 | $0.00260 |
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 9d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Curator
Turn a session's raw bd remember notes into deduplicated, consolidated, well-structured
memories — and prune the pile — using bd over text already in context. No runtime, no embeddings.
Announce at start: "I'm using the memory-curator skill to consolidate and structure the memory store."
When to Use
- Session-close — when the session produced ~3+ new
bd remembercalls. Offered, never automatic. - On-demand — a full-store sweep:
Skill(beads-superpowers:memory-curator).
When NOT to Use
- Sessions with 0–2 new memories — not worth a pass.
- Mid-task — run at a clean stopping point, not while work is in flight.
Memory taxonomy
Two classes; procedural memory (how-to / workflow) lives in the skills, never the memory store.
- semantic — durable facts that stay true.
- episodic — time-bound records of what happened.
The @type is the routing decision. Classify once; the type deterministically sets store, injection, and lifecycle.
@type |
store | injected at session start? | lifecycle |
|---|---|---|---|
semantic:lesson |
memory | yes (salience≥4) | durable; consolidate near-dups |
semantic:root-cause |
memory | yes (salience≥4) | durable; consolidate |
semantic:pattern |
memory | yes (salience≥4) | durable; consolidate |
semantic:correction |
memory | yes | durable (supersedes a wrong memory) |
semantic:research |
deferred knowledge-bead | no | deferred bead; pointer to a research doc (metadata.doc); bd supersede on replacement |
semantic:design |
deferred knowledge-bead | no | deferred bead; pointer to an ADR/spec (metadata.doc); bd supersede on replacement |
semantic:decision |
deferred knowledge-bead | no | deferred bead; pointer to an ADR (metadata.doc); bd supersede on replacement |
episodic:continuation |
memory | latest only | supersede on next |
episodic:done / cleanup / review |
memory → retire | no | consolidate into a semantic fact, then drop; age-out (>30d) safety net |
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.
- 9d ago First seen · 142 lines · 52 tokens per session scan A 44c054252909
memory-curator is a skill published in the GitHub repository DollarDill/beads-superpowers (26 stars, last pushed 17d ago), licensed MIT. It adds 52 tokens to every session and 2,604 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 skills, from other repositories
ucai-patterns
Use when the user asks about Claude Code best practices, how to write agents, how to use hooks, how to manage context, or how to work effectively with Claude Code's native systems.
orient
Use when user invokes /orient with a topic keyword, entity type, project name, time qualifier, or combination. Also triggers on "what do we know about X", "remind me about X", "where did we leave off on X". Provides targeted context loading — searches the MCP Memory Server graph, knowledge files, journal entries, and…
memory
Use when user invokes /memory with a subcommand (search, trace, add, episode, status). Also triggers on "search my memory for X", "add to memory", "what do I know about X" (when membrain is available), "memory status", "memory trace". Searches and manages the membrain knowledge graph via MCP tools or HTTP API.
capture
Use when user invokes /capture to capture information from the current conversation into a staging file for later reflection and knowledge graph processing. Accepts no arguments (auto-extract), specific facts as text, or filter keywords like "decisions" or "technical". Do NOT use when the user wants to write directly…
lembas
Use between workflow phases or when context feels bloated. Writes a structured checkpoint capturing task, findings, files, state, and next steps, then continues from that summary instead of the full history. Invoke standalone or automatically between quest phases.
furl
How the Furl context-compression plugin works in Claude Code and Codex — the furlcompress / furlretrieve / furlstats / furlpurge / furlsearch / furllist MCP tools, the > retrieval flow, and Claude Code's optional automatic hooks. Use when the user asks what Furl is doing, how to compress or retrieve content, why…