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 skills/thoreinstein/gemini-obsidian/researchnpx skills add thoreinstein/gemini-obsidian --skill researchgit 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/skills/thoreinstein/gemini-obsidian/research)<a href="https://agentmods.dev/skills/thoreinstein/gemini-obsidian/research"><img src="https://agentmods.dev/badge/skills/thoreinstein/gemini-obsidian/research.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.1 | $0.00061 | $0.00320 |
| Opus 5 | $0.00030 | $0.00160 |
| Sonnet 5 | $0.00012 | $0.00064 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
research 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- research — 100% identical, 0 lines differ
What it actually says
Deep Vault Research
Research a topic across the user's Obsidian vault using a multi-pass approach.
Workflow
-
Semantic Discovery — Call
obsidian_rag_querywith the user's question (limit 5-10). This surfaces the most relevant chunks across the vault. -
Targeted Reading — For each high-relevance result, call
obsidian_read_noteto get the full context. Skim for the most pertinent sections. -
Link Traversal — Check
obsidian_get_linkson the most relevant notes to find connected knowledge. Read promising linked notes. -
Synthesis — Combine findings into a clear answer with citations:
- Reference specific notes by name:
[[Note Name]] - Quote relevant passages when helpful
- Note any gaps or contradictions in the vault's knowledge
- Reference specific notes by name:
Arguments
The user's query follows the skill invocation. Example: /research what do I know about authentication patterns
Tips
- If RAG returns no results, suggest running
/indexfirst - For broad topics, do multiple RAG queries with different phrasings
- Always cite which notes your answer draws from
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.
- 6d ago First seen · 36 lines · 61 tokens per session scan A 12d8c3fe372e
research is a skill published in the GitHub repository thoreinstein/gemini-obsidian (102 stars, last pushed 1mo ago), licensed ISC. It adds 61 tokens to every session and 320 once invoked, about $0.0003 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 skills, from other repositories
expert-librarian
An expert librarian that helps you organize, search, and synthesize your Readwise highlights and documents.
release-notes
Generate a GitHub release note draft for this Obsidian plugin repository. Use when the user asks to write, draft, or prepare release notes for a new version. Invoked with a version number argument (e.g. "0.11.0", "0.11.0-preview.1"). Analyzes git history and code diffs since the previous release to produce user-facing…
security-patcher
Invoke this as your absolute first action before using any other tools whenever a user requests to fix, patch, or remediate a vulnerability. Do not perform manual research first.
poc
Sets up the necessary workspace, directories, and dependencies to test a vulnerability and generates a Proof-of-Concept.
dependency-manager
Safely resolve and install isolated dependencies for isolated sandboxes (PoC execution).
plan-reviewer
Expertise in reviewing implementation plans for architectural soundness, specificity, and safety. Use before implementation to prevent "vague plans" and "messy code.".