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 allenhutchison/obsidian-gemini --skill deep-researchgit clone --depth 1 https://github.com/allenhutchison/obsidian-geminiWrote 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/allenhutchison/obsidian-gemini/deep-research)<a href="https://agentmods.dev/skills/allenhutchison/obsidian-gemini/deep-research"><img src="https://agentmods.dev/badge/skills/allenhutchison/obsidian-gemini/deep-research/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/allenhutchison/obsidian-gemini/deep-research"><img src="https://agentmods.dev/badge/skills/allenhutchison/obsidian-gemini/deep-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.00739 |
| Opus 5.5 | $0.00019 | $0.00296 |
| Sonnet 5.5 | $0.00009 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
deep-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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Research
Conduct comprehensive, multi-round research using the deep_research tool. This produces structured markdown reports with citations by iteratively searching, reading, and synthesizing multiple sources.
When to Use Deep Research vs Google Search
Use deep_research when... |
Use google_search when... |
|---|---|
| The topic requires synthesis across multiple sources | A quick factual answer is needed |
| The user wants a structured report or overview | The user asks for a single data point |
| Research should combine vault notes with web sources | The user wants current news or events |
| The question is broad or exploratory | The question is specific and narrow |
| The user explicitly asks for "deep research" or "a report" | The user asks "what is..." or "when did..." |
Default to google_search for simple questions. Only use deep_research when the scope genuinely warrants multi-source synthesis.
How to Use
Call the deep_research tool with these parameters:
topic(required) — The research question or topic. Be specific and descriptive.scope(optional) — Where to search:both(default) — Web sources + vault notes. Best for most research.web_only— Internet sources only. Use when the topic is outside the vault's scope.vault_only— Vault notes only. Use to synthesize the user's own notes. Requires Semantic Vault Search to be enabled.
outputFile(optional) — Path to save the report (e.g.,Research/topic-name.md). A.mdextension is added automatically if missing.
If both is requested but Semantic Vault Search isn't configured, the tool gracefully falls back to web-only research.
Best Practices
- Always suggest an
outputFile— Research reports are valuable artifacts. Suggest saving to a logical location likeResearch/or a project folder. - Warn the user about timing — Deep research takes several minutes. Let the user know before invoking the tool.
- Choose the right scope:
- User wants to understand a new external topic →
web_onlyorboth - User wants to synthesize their own notes →
vault_only - User wants to combine personal knowledge with external research →
both
- User wants to understand a new external topic →
- Write a clear topic — Frame the topic as a research question or focused description. "The evolution of transformer architectures in NLP" is better than "transformers".
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.
- 2mo ago First seen · 61 lines · 47 tokens per session scan A 99fa8fe1eb17
deep-research is a skill published in the GitHub repository allenhutchison/obsidian-gemini (534 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 739 once invoked, about $0.0002 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.