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 thoreinstein/gemini-obsidian --skill cross-linkergit clone --depth 1 https://github.com/thoreinstein/gemini-obsidianWrote 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/thoreinstein/gemini-obsidian/cross-linker)<a href="https://agentmods.dev/skills/thoreinstein/gemini-obsidian/cross-linker"><img src="https://agentmods.dev/badge/skills/thoreinstein/gemini-obsidian/cross-linker.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.00864 |
| Opus 5 | $0.00028 | $0.00432 |
| Sonnet 5 | $0.00011 | $0.00173 |
| Haiku 4.5 | $0.00006 | $0.00086 |
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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cross-linker — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Linker
Discover unlinked mentions of vault concepts and insert [[wikilinks]]. Complements link-audit (which finds broken/orphan links) by finding links that should exist but don't.
Workflow
Phase 1 — Build Page Registry
- Call
obsidian_list_noteson the target scope (default:Engineering/). - For each note, call
obsidian_read_noteand extract from frontmatter:- Title (from
# headingor filename) - Aliases (from
aliases:frontmatter field, if present) - Type (pattern, trap, decision, concept)
- Title (from
- Build a registry:
{ title, aliases[], path, type }for each note.
For large scopes (>50 notes), batch reads and process incrementally.
Phase 2 — Scan for Unlinked Mentions
For each note in scope:
- Call
obsidian_read_noteto get the full body text. - For each other page in the registry, check if the page's title or any alias appears in the body text without being wrapped in
[[...]]. - Skip matches inside:
- Existing wikilinks
[[...]] - Code blocks (fenced or inline)
- Frontmatter
- The note's own title/heading
- Existing wikilinks
- Record each match:
{ source_note, target_note, matched_text, line_context, confidence }
Phase 3 — Score and Rank
Assign confidence to each proposed link:
- High — exact title match (case-insensitive), target is a Pattern/Trap/Decision note
- Medium — alias match, or title match in a less structured note
- Low — partial match or only semantically related (use
obsidian_rag_queryto verify)
Sort findings: high confidence first, grouped by source note.
Phase 4 — Present Findings
Show the user a report:
## Cross-Link Report for: Engineering/
### High Confidence (auto-apply)
- Engineering/Patterns/table-driven-tests.md
Line 12: "table driven tests" → [[Table-Driven Tests]]
### Medium Confidence (confirm each)
- Engineering/Traps/mock-drift.md
Line 8: "interface injection" → [[Interface Injection]]
### Low Confidence (review)
- working/appiary/knowledge/auth.md
Line 23: "token" → possibly [[Token Rotation]] ?
### Summary
- X high-confidence links ready to apply
- Y medium-confidence links for review
- Z low-confidence suggestions
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.
- 8d ago First seen · 91 lines · 55 tokens per session scan A 7d993a1c5c30
cross-linker is a skill published in the GitHub repository thoreinstein/gemini-obsidian (102 stars, last pushed 1mo ago), licensed ISC. It adds 55 tokens to every session and 864 once invoked, about $0.0003 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-30.
Other skills, from other repositories
context-optimize
Skill "context-optimize" from Joonghyun-Lee-Frieren/oh-my-antigravity, covering purpose, trigger, workflow, output template and context health.
compound
Extract lessons, patterns, and architectural truths to compound team knowledge.
expert-librarian
An expert librarian that helps you organize, search, and synthesize your Readwise highlights and documents.
memory-management
This skill should be used when the user wants to "persist agent state", "remember past conversations", "short-term memory", "long-term memory", "session management", "vector database for agents", "agent memory", "context window management", "store user preferences", "recall previous interactions", "stateful agents"…
neo4j-agent-memory-skill
Authoritative reference for the neo4j-agent-memory Python package — a graph-native memory system for AI agents built on Neo4j — and for the hosted service (NAMS) at memory.neo4jlabs.com. Use this skill whenever the user mentions neo4j-agent-memory, agent memory with Neo4j, context graphs, the POLE+O model…
context-degradation
Recognize patterns of context failure: lost-in-middle, poisoning, distraction, and clash.