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 s-annam/okfmem --skill okfmem-reindexgit clone --depth 1 https://github.com/s-annam/okfmemWrote 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/s-annam/okfmem/okfmem-reindex)<a href="https://agentmods.dev/skills/s-annam/okfmem/okfmem-reindex"><img src="https://agentmods.dev/badge/skills/s-annam/okfmem/okfmem-reindex/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/s-annam/okfmem/okfmem-reindex"><img src="https://agentmods.dev/badge/skills/s-annam/okfmem/okfmem-reindex.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.00074 | $0.03197 |
| Opus 5.5 | $0.00030 | $0.01279 |
| Sonnet 5.5 | $0.00015 | $0.00639 |
| Haiku 4.5 | $0.00007 | $0.00320 |
Grade A, and why
okfmem-reindex 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.
How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
okfmem Reindex
Names. Canonical
/okfmem-reindex. This skill lives in theokfmemrepo (~/okfmem/skills/);okfmem initsymlinks it into each harness alongside/okfmem,/okfmem-save, and/okfmem-curate.
Restructure a flat MEMORY.md that has grown past the auto-load byte ceiling
into a two-tier index: a small root MEMORY.md that reads as a routing
table, plus one or more MEMORY-<lane>.md lane indexes holding the actual
pointer bulk. Nothing is deleted, archived, or rewritten in content — every
pointer that moves still points at the same page. This is a topology fix, not
a hygiene pass.
Why this is a separate skill from okfmem-curate
okfmem-curate answers "is this content still worth keeping" — it deletes,
archives, and compresses. This skill answers "is this content filed in the
right place" — it only moves pointers between index files. The two operations
have opposite risk profiles:
okfmem-curate |
/okfmem-reindex |
|
|---|---|---|
| Operation | deletes pages | moves a pointer between index files |
| Reversibility | hard; git-backed store is the only recovery | nothing is lost; no page is touched |
| Gate | hard approval stop, deliberately rare | propose → approve → execute; can be routine |
| Framing | rot | topology |
A store can come back from a full curate audit completely clean — zero
superseded markers, zero dangling pointers, every page recent — and still
have a MEMORY.md several times over budget. That is not a curation problem;
curate has no vocabulary for it. Folding a non-destructive move behind
curate's hard stop would also make it rarer than it deserves to be, since a
reversible operation does not need the friction a destructive one does.
Never re-flatten. The remedy for an over-budget MEMORY.md is a lane
split, never tighter hooks — see skills/okfmem-save/SKILL.md Step 3
("Lane routing") and skills/okfmem-curate/SKILL.md Phase 2 for the full
statement of this rule and the byte-savings ratio between the two remedies.
This skill exists to execute that split, not to restate the rule.
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 · 258 lines · 74 tokens per session scan A ea93540bd4a2
okfmem-reindex is a skill published in the GitHub repository s-annam/okfmem (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 3,197 once invoked, about $0.0003 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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…