What is memory-bridge?

A knowledge browser for a Logseq wiki that shows which AI tool created each piece of stored information and lets you compare that knowledge.

Use it to browse knowledge from Codex, Claude, or other tracked tools, search a topic within one tool's pages, and compare two tools' coverage.

It helps you find information by its source and see what one AI tool knows that another does not, instead of treating the whole wiki as one undifferentiated collection.

How ystreibel/logseq-wiki configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to ystreibel/logseq-wiki. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ystreibel/logseq-wiki/main/.skills/memory-bridge/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ystreibel/logseq-wiki

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/memory-bridge/github.svg)](https://agentmods.dev/skills/ystreibel/logseq-wiki/memory-bridge)

Your own site

<a href="https://agentmods.dev/skills/ystreibel/logseq-wiki/memory-bridge"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/memory-bridge/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 134 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,660 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00134	$0.01660
Opus 5.5	$0.00054	$0.00664
Sonnet 5.5	$0.00027	$0.00332
Haiku 4.5	$0.00013	$0.00166

Measured 2mo ago against content hash 9b2629c161a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.skills/memory-bridge/SKILL.md · 164 lines

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 .env in the logseq-wiki repo (fallback); if neither exists, prompt setup. This gives LOGSEQ_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.md for 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 → claude
- codex_rollout, codex_index, codex_history → codex
- hermes_memory, hermes_session → hermes
- openclaw_memory, openclaw_daily_note, openclaw_session, openclaw_dreams → openclaw
- copilot_session, copilot_checkpoint, copilot_transcript, copilot_memory_artifact → copilot
- pi_session → pi
- document → ingest
- anything else → manual
pages_created and pages_updated — the wiki pages that came out of this source

Read the full file on GitHub · 164 lines

Changes

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.

2mo ago First seen · 164 lines · 134 tokens per session scan A 9b2629c161a6

Subscribe to this mod's changes

memory-bridge is a skill published in the GitHub repository ystreibel/logseq-wiki (5 stars, last pushed 11d ago), licensed MIT. It adds 134 tokens to every session and 1,660 once invoked, about $0.0005 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.

Memory and context

memory-bridge next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
memory-bridgeystreibel/logseq-wiki	Skill	5	11d ago	MIT	A	134	Claude Code, Codex
knowledge-ingestopenclaw/openclaw	Skill	394k	today	MIT	A	80	Claude Code, Codex
mem0-oss-to-platformmem0ai/mem0	Skill	68k	2d ago	Apache-2.0	A	217	Claude Code, Codex
forgetasgeirtj/system_prompts_leaks	Skill	71k	2d ago	CC0-1.0	A	74	Claude Code, Codex
Cortexdanielmiessler/LifeOS	Skill	20k	yesterday	MIT	A	184	Claude Code
ha-data-storesshiwenwen/hope-agent	Skill	1.9k	yesterday	MIT	A	115	Claude Code, Codex
memoryopensquilla/opensquilla	Skill	7.1k	6d ago	Apache-2.0	A	44	Claude Code, Codex

logseq-wiki: Skill for Claude Code