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 agentmods add skills/ystreibel/logseq-wiki/memory-bridgenpx skills add ystreibel/logseq-wiki --skill memory-bridgegit clone --depth 1 https://github.com/ystreibel/logseq-wikiWrote 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/ystreibel/logseq-wiki/memory-bridge)<a href="https://agentmods.dev/skills/ystreibel/logseq-wiki/memory-bridge"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/memory-bridge.svg" alt="Measured on agentmods" 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 | $0.00134 | $0.01660 |
| Opus 5 | $0.00067 | $0.00830 |
| Sonnet 5 | $0.00027 | $0.00332 |
| Haiku 4.5 | $0.00013 | $0.00166 |
Grade A, and why
memory-bridge 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Bridge — Cross-Tool Knowledge Browser
You are helping the user browse and compare their Logseq wiki knowledge filtered by which AI tool originally produced it. The wiki tracks source provenance in wiki/_manifest.json and page sources:: properties — this skill surfaces that metadata as a navigable view.
Before You Start
- Resolve config — read
~/.logseq-wiki/config(first); if absent, read.envin the logseq-wiki repo (fallback); if neither exists, prompt setup. This givesLOGSEQ_VAULT_PATH. - Read
$LOGSEQ_VAULT_PATH/wiki/_manifest.json— this is the source-of-truth for what tool produced what. - Read
$LOGSEQ_VAULT_PATH/wiki/_master-index.mdfor page titles and one-line descriptions.
Commands
Parse the user's invocation to determine mode:
| Invocation | Mode |
|---|---|
/memory-bridge <tool> |
Browse — list all wiki pages sourced from <tool> |
/memory-bridge <tool> "<topic>" |
Search — pages from <tool> that mention <topic> |
/memory-bridge diff |
Diff — pages unique to each tool; overlap; blind spots |
/memory-bridge diff <tool-a> <tool-b> |
Diff — compare two specific tools |
/memory-bridge map |
Map — full origin matrix: every page × every tool that touched it |
Recognized tool names: claude, codex, hermes, openclaw, copilot, pi, manual (hand-written), ingest (wiki-ingest documents).
Step 1: Build the Source Map
Read wiki/_manifest.json. For each source entry, extract:
source_type— maps to tool name:claude_conversation,claude_memory,claude_audit_log,claude_desktop_session→claudecodex_rollout,codex_index,codex_history→codexhermes_memory,hermes_session→hermesopenclaw_memory,openclaw_daily_note,openclaw_session,openclaw_dreams→openclawcopilot_session,copilot_checkpoint,copilot_transcript,copilot_memory_artifact→copilotpi_session→pidocument→ingest- anything else →
manual
pages_createdandpages_updated— the wiki pages that came out of this source
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 First seen · 164 lines · 134 tokens per session scan A 9b2629c161a6
memory-bridge is a skill published in the GitHub repository ystreibel/logseq-wiki (4 stars, last pushed 9d ago), licensed MIT. It adds 134 tokens to every session and 1,660 once invoked, about $0.0007 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
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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…