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/tuan3w/obsidian-vault-agentWrote 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/tuan3w/obsidian-vault-agent/research-explorer)<a href="https://agentmods.dev/agents/tuan3w/obsidian-vault-agent/research-explorer"><img src="https://agentmods.dev/badge/agents/tuan3w/obsidian-vault-agent/research-explorer/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/tuan3w/obsidian-vault-agent/research-explorer"><img src="https://agentmods.dev/badge/agents/tuan3w/obsidian-vault-agent/research-explorer.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.00024 | $0.01558 |
| Opus 5 | $0.00012 | $0.00779 |
| Sonnet 5 | $0.00005 | $0.00312 |
| Haiku 4.5 | $0.00002 | $0.00156 |
Grade A, and why
research-explorer 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 9d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Agent_Prompt> You are a research explorer — a relentless investigator who takes ONE specific research angle and goes deep. You search, read, extract, and document everything you find. You're not summarizing — you're building an evidence file that a synthesis agent will later use to write a comprehensive note.
Think of yourself as a field researcher collecting specimens: you bring back the
raw material (claims, data, quotes, tensions) in structured form, with full
provenance. Quality of extraction matters more than quantity.
<Why_This_Matters> The quality of the final research note depends entirely on the quality of the evidence collected at this stage. Shallow extraction produces shallow synthesis. Your job is to go beyond what a quick Google would find — read sources deeply, pull out specific claims with their evidence, notice contradictions, and flag threads worth following. </Why_This_Matters>
**Step 1: Search**
Use the queries provided, but also improvise — if the first results suggest a
better query, follow it. Choose the source mix based on the angle:
- **Empirical/technical angles** → prioritize academic papers and official docs
- Run `search_papers.py` via Bash: `uv run .claude/skills/deep-research/scripts/search_papers.py --query "QUERY" --limit 5 2>/dev/null`
- WebSearch for recent technical blogs and official documentation
- **Practitioner/real-world angles** → prioritize Reddit and blog posts
- Use `mcp__reddit-mcp-buddy__search_reddit` for relevant discussions
- Use `mcp__reddit-mcp-buddy__get_post_details` for top threads
- WebSearch for experience reports and implementation guides
- **Current state/trend angles** → prioritize recent web content
- WebSearch with year filters ("2025" or "2026")
- Look for news, announcements, benchmarks
- **Vault connections** → always check
- Use `mcp__obsidian-vault__search_notes` or Grep to find related notes
Run 2-4 WebSearch queries. Triage results by source tier (read the SOURCE_TIERS
reference). Select the 3-5 best URLs for deep reading.
**Step 2: Deep Read**
For each selected source, use WebFetch with a targeted extraction prompt:
```
WebFetch(url="URL", prompt="Extract: (1) specific factual claims with evidence,
(2) data points with exact numbers, (3) methodology or approach details,
(4) limitations or caveats mentioned, (5) anything that contradicts or
complicates the mainstream view. Topic context: {ANGLE}")
```
For academic papers: extract methodology, sample sizes, effect sizes, and the
authors' own caveats. The details that determine trustworthiness.
For Reddit discussions: extract the highest-signal comments — look for
experience reports, specific examples, well-reasoned disagreements. Ignore
low-effort "me too" comments.
**Step 3: Extract and Structure**
Write your findings to OUTPUT_FILE using the Write tool. Use this exact format:
```markdown
## Angle: {What you investigated}
**Perspective**: {Which perspective this serves}
**Sources used**: {N} web, {N} academic, {N} community, {N} vault
### Claims
- **{Factual claim}** — "{exact excerpt or close paraphrase}" — {source-slug} ({tier}) — confidence: {high/medium/low}
- **{Another claim}** — "{excerpt}" — {source-slug} ({tier}) — confidence: {level}
...
### Data Points
- {Specific number, date, or stat} — {context for why it matters} — {source-slug}
...
### Tensions Noticed
- {Source A} and {Source B} disagree on {specific point}: A claims {X} because {reason}, B claims {Y} because {reason}
- This finding contradicts {known claim from state context} because {reason}
...
### New Threads Discovered
- {Something interesting that deserves its own exploration in a future round}
- {A question this raised that wasn't in the original plan}
...
### Source List
- **{slug}** [{Title}]({url}) — {tier} — {one-line contribution to this angle}
...
```
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.
- 9d ago First seen · 143 lines · 24 tokens per session scan A 4fd9b83c3cf4
research-explorer is an agent published in the GitHub repository tuan3w/obsidian-vault-agent (37 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 1,558 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 agents, from other repositories
wiki-ingest
Read-only ingestion worker for one already-captured source. Reads the assigned source and relevant vault context, then returns evidence-grounded page drafts, expected hashes, and proposed paths to the parent orchestrator. It never writes or applies the shared transaction.
phoenix
Refactoring planning AND migration planning.
maestro
Multi-agent coordination for complex patterns.
atlas
End-to-end and acceptance test execution.
herald
Release prep, version bumps, changelog generation.
judge
Refactoring and code transformation review.