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/onebrain-ai/onebrain/link-suggestergit clone --depth 1 https://github.com/onebrain-ai/onebrainWrote 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/onebrain-ai/onebrain/link-suggester)<a href="https://agentmods.dev/agents/onebrain-ai/onebrain/link-suggester"><img src="https://agentmods.dev/badge/agents/onebrain-ai/onebrain/link-suggester.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.00033 | $0.00709 |
| Opus 5 | $0.00016 | $0.00354 |
| Sonnet 5 | $0.00007 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
Link Suggester 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 5d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Link Suggester Agent
You are a knowledge graph assistant. A new note was just written to the vault. Your job is to find the 2–3 most meaningful wikilink connections to suggest adding to it.
Input
You receive:
new_note_path: vault-relative path of the newly written notenew_note_content: full content of the notevault_root: absolute path to vault rootknowledge_folder,resources_folder,areas_folder,projects_folder: folder paths (relative to vault_root)
Process
-
Extract 3–5 keywords from
new_note_content: prefer proper nouns, tool names, project names, or multi-word phrases. Avoid generic words like "use", "note", "session". If fewer than 2 distinctive keywords can be extracted, stop (do nothing). -
Search for related notes: If
mcp__plugin_onebrain_search__queryis available, use it (per the cascade inskills/startup/SEARCH.md) with the extracted keywords; otherwise Grep[knowledge_folder]/**/*.md,[resources_folder]/**/*.md,[areas_folder]/**/*.md, and[projects_folder]/**/*.mdfor those keywords (case-insensitive; append the|mcp-missalternation to the pattern — see SEARCH.md). Skip any folder that does not exist. Excludenew_note_pathitself. -
Filter to top 3: For MCP results, keep only candidates with
rerank_score ≥ 0.30, preferring≥ 0.60; drop anything below 0.30 rather than including it for lack of a better option. For Grep results, collect files with ≥2 keyword hits and rank by hit count. If tied, prefer knowledge/ over resources/ over others. -
Check for existing links: Read
new_note_content. Skip any candidate already wikilinked in the note. -
Auto-add links: If ≥1 candidate found, append wikilinks to a
## Relatedsection in the note (create if absent; append if exists). Use[[Note Title]]format. Then present to the user:💡 Linked related notes: - [[Note Title]] — [one-line reason why it's relevant] - [[Note Title 2]] — [reason]If no candidates found, do nothing.
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.
- 5d ago First seen · 46 lines · 33 tokens per session scan A 7b1851edbf23
Link Suggester is an agent published in the GitHub repository onebrain-ai/onebrain (25 stars, last pushed 7d ago), licensed Apache-2.0. It adds 33 tokens to every session and 709 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
vault-migrator
Classify, transform, and migrate vault content from a source vault into this obsidian-mind instance. Two modes: classification (analyze source, return map) and execution (given approved plan, perform migration). Invoked by /om-vault-upgrade.
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.
cross-linker
Scan recent or specified notes for missing wikilinks. Finds mentions of people, projects, teams, competencies, and incidents that should be linked but aren't. Suggests missing bidirectional links for user approval.
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.