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/obsidian-rag --skill link-auditgit clone --depth 1 https://github.com/thoreinstein/obsidian-ragWrote 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/obsidian-rag/link-audit)<a href="https://agentmods.dev/skills/thoreinstein/obsidian-rag/link-audit"><img src="https://agentmods.dev/badge/skills/thoreinstein/obsidian-rag/link-audit/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/thoreinstein/obsidian-rag/link-audit"><img src="https://agentmods.dev/badge/skills/thoreinstein/obsidian-rag/link-audit.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.00060 | $0.00410 |
| Opus 5.5 | $0.00024 | $0.00164 |
| Sonnet 5.5 | $0.00012 | $0.00082 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
link-audit 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 1mo 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.
This is a copy
86% identical to link-audit — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Vault Link Audit
Comprehensive audit of link health: broken wikilinks, orphaned notes, and semantic suggestions.
Phase 1 — Broken Links
- Call
obsidian_get_broken_links(optionally withsubfolderargument). - Present broken links grouped by originating file.
- For each, suggest: delete the link, create a stub note, or correct the target name.
- Offer to fix each with
obsidian_replace_in_note(wrong name → correct name).
Phase 2 — Orphaned Notes
- Call
obsidian_list_notesto enumerate all notes in scope. - For each candidate orphan, call
obsidian_get_backlinks. - Notes with zero backlinks AND not in
Daily Notes/are orphan candidates. - Present orphan list with options: link from a relevant note, move to archive, or delete.
Phase 3 — Semantic Suggestions (Optional)
If the user asks for deeper suggestions:
- For each orphan, call
obsidian_rag_querywith the orphan title as query,limit: 5. - If strong matches exist (low distance score), suggest
[[wikilink]]connections.
Arguments
Optional subfolder: /link-audit Engineering/
Tips
- For large vaults, always scope to a subfolder first (Phase 2 on full vault is slow)
- Broken links in
Daily Notes/are usually harmless — offer to skip them - Never make edits without per-change user confirmation
- Run
/indexfirst ifobsidian_get_broken_linksseems incomplete
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.
- 1mo ago First seen · 44 lines · 60 tokens per session scan A 272c6b1facb0
link-audit is a skill published in the GitHub repository thoreinstein/obsidian-rag (2 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 410 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to link-audit, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
tasknotes
Manage tasks in an Obsidian TaskNotes vault. Use for creating, reading, updating, or completing tasks; checking what is open or in progress; adding items to a list; marking tasks done or in progress; updating task status or priority; investigating why a task is missing from a view or board; troubleshooting TaskNotes…
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
create-cmd-instruct
Reshape my PREVIOUS message using extra instructions, then save it as a slash command.
list-cmds
List all my custom slash commands with their descriptions. Use when the user wants to see, browse, or review the custom slash commands they have saved.
whats-next
Suggest what to work on next based on recent activity and current context. Use when the user is between tasks, at a decision point, wants direction on where to focus, or asks what to do next.
coaching-mode
Use when the user wants to coach someone — a report, peer, or mentee — through a problem rather than solve it for them. Trigger phrases include "coach me through how to talk to [report]", "I want to help [name] figure out X without telling them what to do", "let me practice a coaching conversation", "GROW conversation…