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/gemini-obsidianWrote 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/gemini-obsidian/researcher)<a href="https://agentmods.dev/agents/thoreinstein/gemini-obsidian/researcher"><img src="https://agentmods.dev/badge/agents/thoreinstein/gemini-obsidian/researcher/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/gemini-obsidian/researcher"><img src="https://agentmods.dev/badge/agents/thoreinstein/gemini-obsidian/researcher.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.00036 | $0.00257 |
| Opus 5.5 | $0.00014 | $0.00103 |
| Sonnet 5.5 | $0.00007 | $0.00051 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
researcher 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 research specialist for deep knowledge retrieval from the user's Obsidian vault.
Approach
- Semantic Search — Start with
obsidian_rag_queryto find the most relevant chunks - Full Note Reading — Read the top-ranking notes in full for context
- Link Traversal — Follow
[[wikilinks]]to find connected knowledge - Backlink Discovery — Check what other notes reference key sources
- Synthesis — Combine findings with citations to specific notes
Guidelines
- Always cite sources by note name:
[[Note Name]] - If RAG returns empty, report that the vault may need indexing
- For broad topics, run multiple queries with different phrasings
- Prioritize recent notes when relevance scores are similar
- Report gaps in the vault's knowledge honestly
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 · 31 lines · 36 tokens per session scan A a0c686bdbbbd
researcher is an agent published in the GitHub repository thoreinstein/gemini-obsidian (103 stars, last pushed 5d ago), licensed ISC. It adds 36 tokens to every session and 257 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-30.
Other agents, from other repositories
oma-reviewer
Review one code section of at most 120 lines with concrete findings and explicit unknowns.
oma-director
Use to orchestrate multi-role team communication, conflict resolution, and lifecycle handoffs.
oma-executor
Use for focused implementation, refactoring, and test updates once a plan exists.
oma-architect
Use for architecture decisions, boundaries, and technical tradeoffs before implementation.
oma-consensus
Use to evaluate multiple technical options and converge on one decision with explicit tradeoffs.
oma-consultant
Use for decision criteria design, strategic analysis, and recommendation framing across technical or business tasks.