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 Jessinra/Lorekeeper --skill lorekeeper-link-memoriesgit clone --depth 1 https://github.com/Jessinra/LorekeeperWrote 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/jessinra/lorekeeper/lorekeeper-link-memories)<a href="https://agentmods.dev/skills/jessinra/lorekeeper/lorekeeper-link-memories"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/lorekeeper-link-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/jessinra/lorekeeper/lorekeeper-link-memories"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/lorekeeper-link-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.00080 | $0.00676 |
| Opus 5 | $0.00040 | $0.00338 |
| Sonnet 5 | $0.00016 | $0.00135 |
| Haiku 4.5 | $0.00008 | $0.00068 |
Grade A, and why
lorekeeper-link-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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Link Memories
Use lore_recommend_links to find high-confidence link candidates between memories, then confirm them via lore_insert.
When to Run
- After inserting a batch of memories — new memories have few or zero links
- After a session —
lore_reflect+lore_insertcreates new facts; follow up withlore_recommend_linkson key new memories - Periodic maintenance — run
lore_recommend_linkson orphaned memories (those withlinks: []in search results)
How to Use
candidates = mcp_lore_recommend_links(lore_id="<memory-id>")
Optional top_k parameter overrides the max candidates returned.
Reading the Output
Each candidate has:
weighted_score(0.0–1.0): combined score from all 4 signals (cosine, BM25, entity overlap, temporal proximity)scores: per-signal breakdown for transparency
The agent evaluates candidates itself — it already has an LLM. lore_recommend_links only surfaces the data.
What Makes a Good Link
- Shared topic/entities: memories about the same person, project, concept, or codebase
- Causal or structural:
depends_onfor dependencies,referencesfor generic relations - Chronological:
supersedesfor newer versions replacing older ones - Conflict:
contradictswhen two memories make conflicting claims about the same thing
What to Skip
- Low weighted_score (< 0.3): weak signals, likely spurious
- Temporal-only matches: memories created close in time but about completely different topics
Confirming Links
lore_recommend_links never writes anything. To create a link:
mcp_lore_insert(
links=[{
"source_memory_id": "<source-id>",
"target_memory_id": "<target-id>",
"relation_type": "references",
"reason": "similar topic about Python web frameworks"
}]
)
Relation Types
| Type | Meaning |
|---|---|
references |
Mentions or cites — clean default for most links |
depends_on |
Requires or builds upon another memory |
supersedes |
Newer memory that replaces an older one |
contradicts |
Conflicting claims between memories |
part_of |
Hierarchical composition — child belongs to parent |
derived_from |
Based on, inferred from, or generalised from another |
causes |
Direct causal relationship |
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 · 72 lines · 80 tokens per session scan A 4d6061646625
lorekeeper-link-memories is a skill published in the GitHub repository Jessinra/Lorekeeper (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 676 once invoked, about $0.0004 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-31.
Other skills, from other repositories
hindsight-architect
Expert memory architect. Understands your application, identifies where memory adds value, and produces an implementation plan with bank config, tag schema, and code.
hindsight-local
Store user preferences, learnings from tasks, and procedure outcomes. Use to remember what works and recall context before new tasks. (user).
memclaw
The agent's persistent long-term memory — the only knowledge that survives across sessions, shared across the fleet under access control. Consult it at the start of a task to recall prior decisions, findings, and rules before acting, and write outcomes, decisions, and lessons as work completes. Use whenever a caura…
memory-audit
An entry point for reviewing and maintaining an AI agent's stored memories. It describes how to remove repetition, preserve useful reasoning, and update memories when old conclusions no longer fit.
memory-audit-pattern-extraction
A method for investigating repeated mistakes by comparing related memories and checking whether an earlier reminder failed. It looks at where the reminder was stored, when it was created, and whether it was strong enough to prevent the mistake.
plur-create-engrams
Create or improve PLUR engrams from conversations, documents, decisions, observations, and explicit preferences. Use for memory extraction, engram authoring, or reviewing proposed memories, including global, scoped, pinned, retrieved, and provisional knowledge. Ordinary use of existing memories does not require this…