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 bettyguo/obsidian_mcp --skill review-and-linkgit clone --depth 1 https://github.com/bettyguo/obsidian_mcpWrote 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/bettyguo/obsidian_mcp/review-and-link)<a href="https://agentmods.dev/skills/bettyguo/obsidian_mcp/review-and-link"><img src="https://agentmods.dev/badge/skills/bettyguo/obsidian_mcp/review-and-link/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.
<a href="https://agentmods.dev/skills/bettyguo/obsidian_mcp/review-and-link"><img src="https://agentmods.dev/badge/skills/bettyguo/obsidian_mcp/review-and-link.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.00636 |
| Opus 5 | $0.00019 | $0.00318 |
| Sonnet 5 | $0.00008 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
review-and-link 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 12d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
The user has captured notes and wants to integrate them into the link graph. This is the "inbox triage" workflow — small, focused, repeated. Default horizon: last 7 days OR an Inbox/ folder if present.
Procedure
- Call
vault_info. Check if anInbox/(or00 Inbox/,0 Inbox/) folder exists. If yes, use that; if no, uselist_notes(modified_since="7d"). - If more than 15 candidate notes, ask the user how many to review this session (default 5).
- For each candidate, in order of mtime descending:
- Call
read_note(path=candidate). - Call
find_related(seed=candidate, top_k=5)andfind_backlinks(path=candidate). - If the note already has 3+ outgoing wikilinks, skip ("looks integrated") and move on.
- Otherwise: surface to user. Show the note's lead paragraph (truncated to ~200 chars), the top 3 related candidates, and any existing backlinks.
- Propose 1–2 wikilink inserts. The user picks: insert, edit, skip, or "move to MOC X."
- Apply the chosen action via
link_notes(..., confirm=true).
- Call
- After the session, summarize: "Reviewed {N} notes. Inserted {K} links. {M} still untouched."
Output format (per note)
Reviewing: [[Inbox/2026-05-12 Reranking trade-offs]]
Lead: "Cross-encoders dominate on top-100 recall but cost 10× the latency of bi-encoders..."
Top related (not yet linked):
1. [[Bi-encoder vs cross-encoder]] — sim 0.78
2. [[Latency budget for retrieval]] — sim 0.71
3. [[MOCs/RAG research]] — sim 0.64
Proposed insert: `[[Bi-encoder vs cross-encoder]]` near "Cross-encoders dominate..."
Action? (insert / edit / skip / move-to-MOC)
Anti-patterns
- Don't batch more than 5–10 notes per session. The whole point is supervised one-at-a-time review.
- Don't propose links to notes the user has already explicitly skipped this session. Track session-state in your chat reply.
- Don't auto-archive (move to a different folder) without explicit instruction. Linking ≠ archiving.
- Don't summarize the note for the user — they wrote it, they remember it. Just show the lead paragraph and the candidates.
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.
- 12d ago First seen · 48 lines · 38 tokens per session scan A 90c2d9577b95
review-and-link is a skill published in the GitHub repository bettyguo/obsidian_mcp (8 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 636 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-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.