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 tuan3w/obsidian-vault-agent --skill processgit 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/skills/tuan3w/obsidian-vault-agent/process)<a href="https://agentmods.dev/skills/tuan3w/obsidian-vault-agent/process"><img src="https://agentmods.dev/badge/skills/tuan3w/obsidian-vault-agent/process/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/tuan3w/obsidian-vault-agent/process"><img src="https://agentmods.dev/badge/skills/tuan3w/obsidian-vault-agent/process.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.00134 | $0.02914 |
| Opus 5.5 | $0.00054 | $0.01166 |
| Sonnet 5.5 | $0.00027 | $0.00583 |
| Haiku 4.5 | $0.00013 | $0.00291 |
Grade A, and why
process 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.
How it starts
The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill is INTERACTIVE by design. The desirable-difficulty questions in Stage 3 are not optional ceremony — the friction IS the learning. The user's answers shape what gets extracted and how.
<Use_When>
- User has a source note (paper, post, book, lecture, course, clipping) to process
- User wants to extract concepts into Term or Note entries
- User asks what's important in something they've read
- User wants to build wikilink connections from a note into the rest of the vault
- User says "process this", "atomize this", "extract concepts", "what did I learn" </Use_When>
<Do_Not_Use_When>
- User wants to find new papers on a topic (use /paper-discover)
- User wants web research on something new (use /research)
- User wants to synthesize ACROSS multiple existing vault notes (use /synthesize)
- The note is already a Term, Note, or Thought (not a source note) </Do_Not_Use_When>
Stage 1: READ THE SOURCE NOTE
Ask the user which note to process if it's not clear from context. Then read it.
Verify the note type is a source type: paper, post, book, lecture,
course, or a Clipping. If the note is a Term, Note, or Thought, stop and
explain why this workflow doesn't apply.
Read the frontmatter and body:
mcp__obsidian-vault__read_note(path="path/to/note.md")
Or if MCP is unavailable:
Read("/absolute/path/to/note.md")
Stage 2: MARK AS PROCESSING
Update frontmatter to signal active work:
mcp__obsidian-vault__update_frontmatter(
path="path/to/note.md",
updates={"processing_status": "processing", "updated_date": "YYYY-MM-DD"}
)
Stage 3: ASK DESIRABLE-DIFFICULTY QUESTIONS
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 · 321 lines · 134 tokens per session scan A 588bdb293c27
process is a skill published in the GitHub repository tuan3w/obsidian-vault-agent (41 stars, last pushed 7mo ago), licensed MIT. It adds 134 tokens to every session and 2,914 once invoked, about $0.0005 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
show-me
Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.
documentation-writer
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework. Templates for tutorial / how-to / reference / explanation live under templates/.
gh-discussions
A guide for answering GitHub Discussions, a question-and-answer area separate from issue reports. In its Q&A categories, a maintainer can mark a reply as the accepted answer.
brain-onboard
An onboarding workflow that helps another person create and use their own private knowledge store, sometimes called a second brain. It gathers their information with consent, saves it in their own workspace, and demonstrates a first useful result.
notebooklm
Drive NotebookLM over a programmatic CLI with no browser: turn a vault slice into an audio overview, study guide or mind map, and fold the artifacts back into the vault. Browser automation is the fallback if CLI auth breaks. Triggers: "/notebooklm", "make an audio digest of ", "podcast from the vault".
interview-prep
An interview preparation workflow that researches a company and role, checks them against your CV, and prepares an English introduction, answers, questions, and practical details.