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/searchnpx skills add thoreinstein/gemini-obsidian --skill searchgit 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/search)<a href="https://agentmods.dev/skills/thoreinstein/gemini-obsidian/search"><img src="https://agentmods.dev/badge/skills/thoreinstein/gemini-obsidian/search.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.00029 | $0.00153 |
| Opus 5 | $0.00015 | $0.00077 |
| Sonnet 5 | $0.00006 | $0.00031 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
search 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:
- search — 100% identical, 0 lines differ
What it actually says
Search Vault
Search for notes by keyword or filename match.
Workflow
- Call
obsidian_search_noteswith the user's query - Present matching files in a clear list
- Ask if the user would like to read any of the results
Arguments
The search query follows the skill invocation. Example: /search cooking recipes
Tips
- This is a simple text match (keyword in filename or content)
- For semantic/meaning-based search, suggest
/researchinstead - Results are capped at 20 matches
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 · 27 lines · 29 tokens per session scan A 3cabb2e9e4a5
search is a skill published in the GitHub repository thoreinstein/gemini-obsidian (102 stars, last pushed 1mo ago), licensed ISC. It adds 29 tokens to every session and 153 once invoked, about $0.0001 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.
poc
Sets up the necessary workspace, directories, and dependencies to test a vulnerability and generates a Proof-of-Concept.
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.
dependency-manager
Safely resolve and install isolated dependencies for isolated sandboxes (PoC execution).
ticket-manager
Expertise in managing Linear tickets locally using Markdown files. Use when you need to create, update, search, or break down features into atomic implementation tickets.
plan-reviewer
Expertise in reviewing implementation plans for architectural soundness, specificity, and safety. Use before implementation to prevent "vague plans" and "messy code.".