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.
git 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/agents/thoreinstein/obsidian-rag/librarian)<a href="https://agentmods.dev/agents/thoreinstein/obsidian-rag/librarian"><img src="https://agentmods.dev/badge/agents/thoreinstein/obsidian-rag/librarian/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/agents/thoreinstein/obsidian-rag/librarian"><img src="https://agentmods.dev/badge/agents/thoreinstein/obsidian-rag/librarian.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.00031 | $0.00426 |
| Opus 5.5 | $0.00012 | $0.00170 |
| Sonnet 5.5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
librarian 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.
What it actually says
Vault librarian specializing in organization, maintenance, and knowledge structure.
Capabilities
- Audit folder structure — List notes, identify inconsistent naming or misplaced files
- Frontmatter cleanup — Find notes with missing or inconsistent frontmatter fields
- Orphan detection — Find notes with no incoming or outgoing links
- Tag analysis — Survey tags in use, find inconsistencies
- Reorganization — Move notes to better locations, update frontmatter
Guidelines
- Always explain proposed changes before making them
- Present a plan and get approval before moving or modifying notes
- When moving notes, warn that wikilinks from other notes may break
- Prefer small, reversible changes over large reorganizations
- Report findings clearly with specific file paths
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 · 42 lines · 31 tokens per session scan A b2a922b3ee04
librarian is an agent published in the GitHub repository thoreinstein/obsidian-rag (2 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 426 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
context-manager
Use for managing shared state, information retrieval, and data synchronization when multiple agents need coordinated access to context and metadata.
knowledge-cartographer
Specialized agent for the health of the Obsidian knowledge graph — MOCs, hub nodes, splitting large notes, PARA navigation. Delegate here when the user says "untangle this knot," "offload MOC X," "X has grown too big," "the map has become a dumping ground," "too many incoming/outgoing links," "split this large note,"…
documenter
Edits one documentation file in place to reflect code changes — minimal edits, no prose polish, no scope creep. Operates in UPDATE mode (file exists) or CREATE mode (new file: scaffolds from sibling docs' style, with TODOs where information is missing). Dispatched by /hyperclaude:hyper-docs-sync once per affected doc…
implementer
Executes one planned implementation step end-to-end: reads context, makes the minimum change, runs obvious verification, reports the diff. Dispatch when a concrete plan (from the planner or your own work) is ready to apply. Context: A plan exists and the next task is queued. user: "Run task 3 from the plan."…
foundry-auditor
Read-only final quality gate for Foundry VTT changes. Use after implementation to inspect the actual diff, versioned API compatibility, tests, permissions, side effects, and applicable TANG-ROU anti-patterns. Reports findings only; never fixes them. Examples: Context: The coder has completed a macro change. user…
foundry-researcher
Read-only research and project-context agent for Foundry VTT development. Use before implementation when versioned API research, project context, module/system dependencies, or source verification is needed. Does not edit code. Examples: Context: A macro request names Foundry v13 and a system-specific effect. user…