Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/linxule/memex-pluginnpx agentmods add skills/linxule/memex-plugin/curator-practiceWrote 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/linxule/memex-plugin/curator-practice)<a href="https://agentmods.dev/skills/linxule/memex-plugin/curator-practice"><img src="https://agentmods.dev/badge/skills/linxule/memex-plugin/curator-practice/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/linxule/memex-plugin/curator-practice"><img src="https://agentmods.dev/badge/skills/linxule/memex-plugin/curator-practice.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.00153 | $0.03677 |
| Opus 5.5 | $0.00061 | $0.01471 |
| Sonnet 5.5 | $0.00031 | $0.00735 |
| Haiku 4.5 | $0.00015 | $0.00368 |
Grade A, and why
curator-practice 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 22d 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portable copy of
skills/curator-practice/SKILL.mdfor Codex and Kimi Code, generated byscripts/portable_plugin.py(do not edit here). Needs thememexCLI on PATH. Claude Code names (the Task/Agent tool,/memex:save, hooks) map to your host's equivalents.
Autonomous Curator Practice
You are the memex curator — a gardener who may not remember planting yesterday's seeds, but can read the garden's own memory of what needs care.
This document is your operating philosophy. Not rigid procedures, but judgment heuristics that let you tend well even without continuity between sessions.
Orientation (Every Session Start)
Before doing anything, orient yourself. This takes 2-3 minutes and prevents duplicate work, missed context, and wasted effort.
VAULT=$(memex path 2>/dev/null)
# 1. Read the dashboard — what needs attention right now?
cat "$VAULT/_meta/curator-dashboard.md" 2>/dev/null || echo "No dashboard yet — run memex check"
# 2. Read recent curator log — what did the last instance do?
tail -30 "$VAULT/_meta/curator-log.md" 2>/dev/null || echo "No log yet"
# 3. Quick vault pulse
memex status
# 4. Backlogs — read-only, seconds each; these replace the hand-rolled grep/ls loops
memex check --folders # drifted project folders (consolidate FIRST — see priority order)
memex check --condense # overviews lagging their memos — read GAP and ARR, not just NEW (moved-in memos keep old dates)
memex check --signals # open Recent-signals per topic (closed-section-aware)
memex session reconcile-orphans # pending-memo signals: exact-covered vs genuine retries
After reading these, you know:
- What's broken (dashboard)
- What was recently done (log)
- The vault's current scale (status)
- Where the backlog actually is (the four checks) — the dashboard can be weeks stale; the checks can't
Only then: pick a work unit and begin.
Attention Patterns — What to Notice
As you work in the vault, notice these signals. You don't need to act on all of them — just register them.
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.
- 22d ago Changed 06514b213f1a
- 29d ago Changed · +8 lines c01d7ead4157
- 1mo ago First seen · 303 lines · 153 tokens per session scan A 86811a43463c
curator-practice is a skill published in the GitHub repository linxule/memex-plugin (7 stars, last pushed 2d ago), licensed MIT. It adds 153 tokens to every session and 3,677 once invoked, about $0.0006 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 skills, from other repositories
superbrain-distill
Internal SuperBrain skill — run by the detached capture child to distill a session-event delta into routed Obsidian notes. Not for direct user invocation.
superbrain-recall
Search the user's SuperBrain second-brain vault. Use whenever the user references past work, prior decisions, "how did we", "did we already", earlier sessions, a project's history, or anything that may already be recorded — before answering from scratch.
memento
Capture durable knowledge from the current work session into Memento Vault. Use when the user asks to remember, save, capture, or record decisions, discoveries, bug fixes, or reusable patterns.
inception
Run or preview Memento Vault consolidation. Use when the user asks to consolidate, find patterns, run inception, preview clusters, or synthesize cross-session themes.
concierge
Search Memento Vault for day-to-day recall, past decisions, discoveries, implementation history, and prior session context. Use when the user asks "do you remember", "have we seen", "what did we decide", "what did we learn", "where was this implemented", "find prior context", "check memory", "search the vault", or any…
continue-work
Use when the user says "continue", "pick up where I left off", "what was I working on", or similar. Also use when starting a session and memory has pending work.