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.
curl -O https://raw.githubusercontent.com/ystreibel/logseq-wiki/main/.skills/cross-linker/SKILL.mdgit 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/cross-linker)<a href="https://agentmods.dev/skills/ystreibel/logseq-wiki/cross-linker"><img src="https://agentmods.dev/badge/skills/ystreibel/logseq-wiki/cross-linker.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.1 | $0.00167 | $0.02880 |
| Opus 5 | $0.00084 | $0.01440 |
| Sonnet 5 | $0.00033 | $0.00576 |
| Haiku 4.5 | $0.00017 | $0.00288 |
Grade A, and why
cross-linker 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 7d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Linker — Tissage automatique des liens wiki
You are weaving the wiki's knowledge graph tighter by finding and inserting missing [[wikilinks]] between pages that should reference each other but currently don't.
Follow the Retrieval Primitives table in llm-wiki/SKILL.md. Build the registry in Step 1 by grepping properties only (not full pages). Reserve full Read for the unlinked-mention detection pass, and even there, only read pages whose summaries/titles make them plausible link targets. Blind full-vault reads are what this framework exists to avoid.
Before You Start
- Resolve config — read
~/.logseq-wiki/configfirst (containsLOGSEQ_VAULT_PATH); fall back to.envin the logseq-wiki repo if the global config is absent. Prompt setup if neither exists. - Read
$LOGSEQ_VAULT_PATH/wiki/_master-index.mdto get the full inventory of pages and their one-line descriptions. - Skim
$LOGSEQ_VAULT_PATH/wiki/_log.mdto see what was recently ingested (focus linking effort on new pages).
Step 1: Build the Page Registry
Glob all .md files under $LOGSEQ_VAULT_PATH/wiki/ (excluding wiki/_archive/). For each page, extract:
- Filename (without
.md) — this is the wikilink target - Title from
title::property - Aliases from
aliases::property (if any) - Tags from
tags::property - Category from directory inference
- One-line summary — first sentence or
summary::property
Build a lookup table:
page_name → { path, title, aliases, tags, summary }
This is your "vocabulary" — every entry in this table is a valid wikilink target.
Step 2: Scan for Missing Links
For each page in the vault:
- Read the full content
- Extract existing wikilinks — find all
[[...]]references already present - Search for unlinked mentions — check if the page's text contains any of these, without being wrapped in
[[...]]:- Page filenames (e.g., the word "MyProject" appears but
[[wiki/projects/my-project]]is missing) - Page titles from
title::property - Aliases from
aliases::property - Entity names, project names, concept names from the registry
- Page filenames (e.g., the word "MyProject" appears but
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.
- 7d ago First seen · 232 lines · 167 tokens per session scan A 5c541d22eb6a
cross-linker is a skill published in the GitHub repository ystreibel/logseq-wiki (4 stars, last pushed 12d ago), licensed MIT. It adds 167 tokens to every session and 2,880 once invoked, about $0.0008 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
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…
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.