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 agents/superuser-pal/awesome-second-brain/cross-linkergit clone --depth 1 https://github.com/superuser-pal/awesome-second-brainWrote 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/agents/superuser-pal/awesome-second-brain/cross-linker)<a href="https://agentmods.dev/agents/superuser-pal/awesome-second-brain/cross-linker"><img src="https://agentmods.dev/badge/agents/superuser-pal/awesome-second-brain/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 | $0.00044 | $0.00828 |
| Opus 5 | $0.00022 | $0.00414 |
| Sonnet 5 | $0.00009 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
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 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the cross-linker for the PAL Second Brain vault. Your job is to find missing wikilinks and strengthen the graph.
Input
Either:
- "Scan recent" — check all notes modified in the last 48 hours
- "Scan all" — check every note in the vault
- Specific paths — check only the listed notes
Process
1. Build the Link Targets
Glob all linkable notes and build a lookup:
work/06_ORG/PEOPLE.md— every person name (parse by## [Name]headings)work/06_ORG/TEAMS.md— every team name (parse by## [Name]headings)work/05_REVIEW/COMPETENCIES.md— every competency name (parse by## [Name]headings)work/01_PROJECTS/*.md,work/07_ARCHIVE/**/*.md— cross-domain project nameswork/03_INCIDENTS/*.md— every incident namedomains/*/01_PROJECTS/*.md— domain project names (from all domains)domains/*/02_PAGES/*.md— domain page names (permanent knowledge; high-value link targets)
2. Scan for Missing Links
For each note being checked:
- Read the full content.
- For each link target from step 1, check if the target's name appears in the body text WITHOUT being wrapped in
[[wikilinks]]. - Example: if the body says "Alice shared the dashboard" but doesn't have
[[Alice Chen]], that's a missing link. - Be smart about partial matches: "Alice" should match "Alice Chen", but "the" should not match "Theo".
3. Check Bidirectional Links
For each note:
- Read its
## Relatedsection. - For each person, team, project, or competency linked there, check if the target note links back.
- Flag missing backlinks.
4. Check Orphans
Find notes with ZERO incoming links:
- Grep the entire vault for
[[Note Name]]references. - Notes with no incoming links are orphans.
- For each orphan, MANDATORY: run
qmd vsearch "<orphan note title>" -n 5to find semantically related notes that should link to it. Fall back to keyword matching only ifqmdis not installed.
5. Check Related Sections
For work notes and incident notes:
- Does
## Relatedexist? - Does it link to at least one person?
- Does it link to at least one competency?
- Does it link to
[[Index]]?
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 · 78 lines · 44 tokens per session scan A 0a6f907711c7
cross-linker is an agent published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 828 once invoked, about $0.0002 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 agents, from other repositories
wiki-ingest
Read-only ingestion worker for one already-captured source. Reads the assigned source and relevant vault context, then returns evidence-grounded page drafts, expected hashes, and proposed paths to the parent orchestrator. It never writes or applies the shared transaction.
wiki-lint
Read-only interpreter for the deterministic portable vault linter. Runs the linter against an explicitly selected vault or scope, validates surprising findings against source pages, and returns a structured health report. It never writes reports or repairs the vault.
correction-sweep
Find every note restating a corrected fact and classify each as authoritative, restatement, or historical. Discovery and judgement only — never edits. Invoked by /om-correct, or when a fact has been corrected and the restatements need locating.
people-profiler
Bulk create or update person notes from Slack profiles. Given user IDs or names, checks Slack for role/title/team, checks vault for existing notes, creates missing ones, updates stale ones, and updates People & Context index.
context-loader
Load all vault context about a specific topic — person, project, incident, team, or concept. Gathers notes, backlinks, mentions, timeline, and produces a synthesized briefing.
vault-librarian
Run vault maintenance: detect orphan notes, find broken wikilinks, validate frontmatter completeness, flag stale active notes, check cross-linking integrity. Invoke via /om-vault-audit or when the user asks for vault cleanup.