pkm-explore

pkm-explore is a skill for Claude Code from AdrianV101/obsidian-pkm-plugin. It costs 55 tokens per session (966 once invoked), scanned A, original, MIT.

A knowledge-base exploration tool that searches notes by meaning and follows their links to map what your vault already contains about a topic.

In plain words
What is it for?
Use it to investigate a topic in a personal knowledge vault, find relevant notes, and identify gaps worth researching.
Why use it?
It helps you avoid repeating research and reveals related notes or missing connections before you create new material.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the vault-pkm plugin — 6 skills, 2 commands, 3 agents, 2 hooks shipped together

Good fit Use it to investigate a topic in a personal knowledge vault, find relevant notes, and identify gaps worth researching.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/adrianv101/obsidian-pkm-plugin/pkm-explore
Install

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.

Any agent
npx skills add AdrianV101/obsidian-pkm-plugin --skill pkm-explore
Clone the repo
git clone --depth 1 https://github.com/AdrianV101/obsidian-pkm-plugin

Made for: Claude Code.

Or install vault-pkm, the plugin that ships this one along with the rest of its 6 skills, 2 commands, 3 agents, 2 hooks.

Wrote 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.

agentmods badge for pkm-explore

README.md
[![agentmods](https://agentmods.dev/badge/skills/adrianv101/obsidian-pkm-plugin/pkm-explore.svg)](https://agentmods.dev/skills/adrianv101/obsidian-pkm-plugin/pkm-explore)
Your own site
<a href="https://agentmods.dev/skills/adrianv101/obsidian-pkm-plugin/pkm-explore"><img src="https://agentmods.dev/badge/skills/adrianv101/obsidian-pkm-plugin/pkm-explore.svg" alt="Measured on agentmods" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 966 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.00966
Opus 5 $0.00028 $0.00483
Sonnet 5 $0.00011 $0.00193
Haiku 4.5 $0.00006 $0.00097

Measured 8d ago against content hash a9624ee52421, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

pkm-explore 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 8d 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.

skills/pkm-explore/SKILL.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PKM Explore — Knowledge Discovery and Gap Analysis

Understand what the vault already knows about a topic before creating new notes or doing research. Combines graph traversal with semantic search to find both explicit connections and hidden relationships.

When to use: Researching vault knowledge on a topic, finding related notes, exploring a topic area before writing.

Step 1: Identify Seed Note

Find the most relevant existing note for the topic:

vault_semantic_search({ query: "<topic>", limit: 5 })

A note on score interpretation. vault_semantic_search uses text-embedding-3-large (3072-dim) cosine similarity, which compresses hard. In a typical vault, even genuinely on-topic notes score around 0.45–0.65, and tangential notes that share surface tokens (e.g., "vibration" matching a "vibe coding" note) often score 0.40–0.45 too. Absolute scores cannot reliably separate "topically relevant seed" from "tangential surface match" — you must read and judge.

Routing:

  • If a specific note path was provided, use that directly as the seed.
  • Otherwise: read the top result with vault_read and judge whether it is topically relevant to the query (not just sharing surface tokens). If yes, use it as the seed and advance to Step 2.
  • If the top result is tangential or off-topic, corroborate with one vault_search keyword query using a distinctive term from the topic. If vault_search returns zero matches AND the semantic top hits are all tangential on read, the vault has minimal coverage — report that and suggest creating a seed note using pkm-write. Do not advance into Steps 2–5 and do not synthesize from tangential matches.

If vault_semantic_search is unavailable (no OPENAI_API_KEY), use vault_search with key terms and vault_query by tags/type to locate a seed note.

Step 2: Graph Context

Explore the structural neighborhood around the seed note:

vault_neighborhood({ path: "<seed-note-path>", depth: 2, direction: "both" })

Read the full file on GitHub · 70 lines

Changes

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.

  1. 8d ago First seen · 70 lines · 55 tokens per session scan A a9624ee52421

Subscribe to this mod's changes

pkm-explore is a skill published in the GitHub repository AdrianV101/obsidian-pkm-plugin (13 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 966 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

lint-brain

Run health checks over the brain vault - find orphan notes, broken wikilinks, missing frontmatter, stale projects, and missing cross-links. Use when asked to "lint the brain", "health check", "vault hygiene", or "/lint-brain".

michaeljauk/brain-starter · 56 tokens

ingest-article

Ingest an article from a URL or raw text into the brain vault. Extracts key knowledge, determines placement, creates or updates notes, and links to relevant projects. Use when the user shares a URL or text and wants to absorb it into their knowledge base.

michaeljauk/brain-starter · 58 tokens

wrap-session-up

End-of-session review for a Claude Code conversation. Replays what was discussed, checks for open action items, documents relevant outcomes in the brain vault, and creates Todoist tasks for anything untracked. Use at the end of a work session to ensure nothing falls through the cracks.

michaeljauk/brain-starter · 60 tokens

kickoff

Guided first-run setup for a forked brain-starter vault. Walks through identity, first project, semantic search, integrations, indexes, and the first commit - verifying each phase before moving on. Use when the user has just forked or cloned brain-starter, says "set up my brain", "I just forked brain-starter", or runs…

michaeljauk/brain-starter · 80 tokens

project-sync

On-demand AI-powered sync of a project's repo state into the brain vault. Reads live git/GitHub/Jira data, updates the project status doc, and makes targeted edits to relevant brain docs where content is clearly stale. Triggered by "/project-sync [name]", "sync [project]", "what's the current state of [project]".

michaeljauk/brain-starter · 73 tokens

save-answer

File a conversation output (research, analysis, comparison, framework) back into the brain vault so it compounds instead of vanishing into chat history. Use when the user says "save this", "file this", "keep this", or when a valuable answer should persist.

michaeljauk/brain-starter · 57 tokens