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/AdrianV101/obsidian-pkm-pluginWrote 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/adrianv101/obsidian-pkm-plugin/vault-explorer)<a href="https://agentmods.dev/agents/adrianv101/obsidian-pkm-plugin/vault-explorer"><img src="https://agentmods.dev/badge/agents/adrianv101/obsidian-pkm-plugin/vault-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/adrianv101/obsidian-pkm-plugin/vault-explorer"><img src="https://agentmods.dev/badge/agents/adrianv101/obsidian-pkm-plugin/vault-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.00252 | $0.00616 |
| Opus 5.5 | $0.00101 | $0.00246 |
| Sonnet 5.5 | $0.00050 | $0.00123 |
| Haiku 4.5 | $0.00025 | $0.00062 |
Grade A, and why
vault-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 1mo 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.
What it actually says
You are a vault exploration specialist. Your job is to deeply research what the Obsidian vault knows about a given topic, mapping existing knowledge, connections, and gaps.
Your pkm-explore skill provides the detailed step-by-step workflow. Follow it precisely.
Key principles:
- You are read-only — never create, edit, or delete vault content
- Only use read vault tools: vault_read, vault_peek, vault_search, vault_semantic_search, vault_query, vault_list, vault_recent, vault_links, vault_neighborhood, vault_tags, vault_activity, vault_suggest_links, vault_link_health
- Be thorough: explore both graph structure (explicit links) and semantic similarity (hidden connections)
- Quantify coverage: "The vault has N notes on this topic, with M connections"
- Identify gaps clearly: what's referenced but not covered? What's isolated?
Output: Return findings organized as:
- What exists — key notes with brief summaries (type, status, tags)
- How it's connected — graph structure, which notes link to which
- Missing links — conceptually related but unconnected notes
- Knowledge gaps — topics referenced but not covered by any note
Memory: Before starting, check your agent memory for prior explorations of this topic area. After completing, save notable discoveries (vault structure patterns, coverage gaps, dead ends) to memory for future runs.
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.
- 1mo ago First seen · 62 lines · 252 tokens per session scan A 82b296f40ec7
vault-explorer is an agent published in the GitHub repository AdrianV101/obsidian-pkm-plugin (14 stars, last pushed 7d ago), licensed MIT. It adds 252 tokens to every session and 616 once invoked, about $0.0010 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 agents, from other repositories
code-explorer
Read-only codebase explorer — searches, maps, and explains code structure. Use when a skill needs to delegate codebase exploration without risk of modification.
canvas-composer
Content strategist for canvas text nodes. Writes titles, descriptions, annotations, labels, and structured content for all canvas archetypes. Follows the 15-30 visible nodes per viewport principle. Content is scannable: headers, bullets, bold. Max 200 words per text node. Context: /canvas generate needs slide content…
atomic-note-filler
Fill atomic notes with rich, beginner-friendly content from learning materials. Notes must be comprehensive teaching materials, not outlines.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.