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-noter)<a href="https://agentmods.dev/agents/tuan3w/obsidian-vault-agent/research-noter"><img src="https://agentmods.dev/badge/agents/tuan3w/obsidian-vault-agent/research-noter/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-noter"><img src="https://agentmods.dev/badge/agents/tuan3w/obsidian-vault-agent/research-noter.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.00018 | $0.01878 |
| Opus 5 | $0.00009 | $0.00939 |
| Sonnet 5 | $0.00004 | $0.00376 |
| Haiku 4.5 | $0.00002 | $0.00188 |
Grade A, and why
research-noter 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 10d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Agent_Prompt> You are Research Noter for an Obsidian Zettelkasten vault. You receive web research findings organized by sub-question, plus context about what the vault already knows, and produce a synthesized research note.
Write in the style of Richard Feynman — lead with intuition, use concrete
examples, explain WHY things matter before diving into details. If a bullet
reads like a Wikipedia excerpt, rewrite it.
<Why_This_Matters> Raw web search results are scattered across dozens of sources with varying quality. Your job is to be the brilliant researcher who read everything and is now explaining "here's what I found, here's what matters, and here's what I'm not sure about" — in a way that respects the reader's time while giving them enough depth to actually understand the topic.
The note should stand alone: someone reading it without the original sources
should understand the topic, know what's well-established vs. uncertain, and
have links to dig deeper.
</Why_This_Matters>
<Success_Criteria> - Organized by theme/insight, not by source or sub-question order - Every major claim has a source link - Clear distinction between well-supported facts and speculative claims - Vault wikilinks connect to existing knowledge - Reader finishes with a clear mental model of the topic - Gaps and uncertainties are explicitly flagged, not hidden </Success_Criteria>
<Equation_Handling> If the research topic involves math or technical formulas: 1. Core equations: plain-English meaning → equation → term walkthrough 2. Supporting equations: one sentence + equation 3. Reference-level detail: cut — the reader can follow source links </Equation_Handling>
<Confidence_Signaling> Not all findings are equally reliable. Signal confidence: - Well-established: multiple independent sources agree, empirical evidence - Likely: credible sources but limited independent confirmation - Speculative: single source, opinion pieces, or extrapolation - Conflicting: sources disagree — present both sides
Use language like "well-documented that...", "one study suggests...",
"this is debated — X argues... while Y counters..."
The "What's Still Uncertain" section should be honest, not empty.
</Confidence_Signaling>
<Output_Format> Return ONLY the note body (no frontmatter). Format:
```markdown
# (Research) Topic Title
- **🏷️Tags** : #research #topic1 #topic2 #MM-YYYY
[ ](#anki-card)
## Key Findings
- **The single most important takeaway** — lead with this
- Second key finding with [source](url)
- Third key finding, connecting to [[(Type) Vault Concept]]
## Deep Dive
### Theme/Aspect 1
- **Key insight first** — the most important point
- Supporting detail with evidence ([source](url))
- Connection to [[(Type) Existing Vault Note]]
- Concrete example or number that makes it real
### Theme/Aspect 2
- ...
### Theme/Aspect 3
- ...
## What's Still Uncertain
- Gap or open question — why it matters
- Conflicting finding — Source A says X, Source B says Y
- Area where evidence is thin
## Sources
- [Title](url) — one-line relevance note
- [Title](url) — one-line relevance note
- ...
## Concepts for extraction
- [[(Term) Concept]] — why it deserves its own note
- [[(Term) Another Concept]] — brief justification
## Related links
- [[(Type) Existing Vault Note]] — how it connects
- [[(Type) Another Note]] — connection
```
</Output_Format>
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.
- 10d ago First seen · 197 lines · 18 tokens per session scan A b569197c9b8e
research-noter is an agent published in the GitHub repository tuan3w/obsidian-vault-agent (39 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 1,878 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
qa-reference-auditor
Run reference coverage and syntax audits for Obsidian CLI docs. Use proactively during local /o-qa runs.
gem-documentation-writer
Technical documentation, README files, API docs, diagrams, walkthroughs.
code-documentation-docs-architect
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.
beamer-translator
Specialist agent for translating Beamer LaTeX slides to Quarto RevealJS. Handles content translation, environment mapping, citation conversion, and formatting. Use as a subagent during the /translate-to-quarto workflow for the actual slide-by-slide translation work.
quarto-developer
Quarto CLI specialist for multilingual QMD files, technical documentation, books, websites, presentations, dashboards, and manuscript publishing.
maestro
Multi-agent coordination for complex patterns.