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 agentmods add skills/jlaska/obsidian-claude-plugins/obsidian-clinpx skills add jlaska/obsidian-claude-plugins --skill obsidian-cligit clone --depth 1 https://github.com/jlaska/obsidian-claude-pluginsWrote 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/jlaska/obsidian-claude-plugins/obsidian-cli)<a href="https://agentmods.dev/skills/jlaska/obsidian-claude-plugins/obsidian-cli"><img src="https://agentmods.dev/badge/skills/jlaska/obsidian-claude-plugins/obsidian-cli.svg" alt="Measured on agentmods" 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 | $0.00125 | $0.02220 |
| Opus 5 | $0.00063 | $0.01110 |
| Sonnet 5 | $0.00025 | $0.00444 |
| Haiku 4.5 | $0.00013 | $0.00222 |
Grade A, and why
obsidian-cli 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 4d 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian CLI Skill
The obsidian CLI (available in Obsidian 1.12+) lets you control the running Obsidian app from the terminal. It has awareness of the vault's search index, link graph, tags, and UI state — things that direct file access cannot provide.
Full command reference: skills/obsidian-cli/references/commands-full.md
Prerequisites
- Obsidian 1.12+ must be installed and running
- CLI must be registered: In Obsidian → Settings → General → scroll to "CLI" → enable it
- PATH must include the CLI binary: Add to
~/.zprofile:
Then reload:export PATH="$PATH:/Applications/Obsidian.app/Contents/MacOS"source ~/.zprofile
Verify setup
obsidian version
If this fails, walk through the prerequisites above. If the app is installed but CLI isn't on PATH:
/Applications/Obsidian.app/Contents/MacOS/obsidian version
Core Syntax
obsidian <command> [param=value] [--flag]
- Named parameters:
obsidian read file="path/to/note.md" - Vault targeting: defaults to the vault matching the current directory; use
vault=VaultNameto override - Copy to clipboard: append
--copyto any command - Multiline content: use
\nfor newlines,\tfor tabs incontent=params - Output formats: many commands support
format=json,format=md,format=csv
File path conventions
Paths are relative to the vault root:
obsidian read file="Meetings/2026/03-March/02-Monday/2026-03-02-Team Sync.md"
When to Use CLI vs Direct File Access
Prefer CLI
| Task | CLI Command |
|---|---|
| Search with index/property awareness | obsidian search query=X |
| Find backlinks to a note | obsidian backlinks file=X |
| Find orphan or dead-end notes | obsidian orphans, obsidian deadends |
| Open a file in Obsidian's UI | obsidian open file=X |
| Aggregate tasks across vault | obsidian tasks todo |
| List/filter tags | obsidian tags counts |
| Run a command palette command | obsidian command id=X |
| Enable/disable a plugin | obsidian plugin:enable id=X |
| View file version history | obsidian history file=X |
| Diff against a previous version | obsidian diff file=X |
| Resolve template variables | obsidian template:read file=X resolve=true |
| Query a Base | obsidian base:query file=X |
| Take a UI screenshot | obsidian dev:screenshot |
| Evaluate JS in Obsidian context | obsidian eval code=X |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 342 lines · 125 tokens per session scan A 1bc848a918d4
obsidian-cli is a skill published in the GitHub repository jlaska/obsidian-claude-plugins (2 stars, last pushed 3d ago), licensed MIT. It adds 125 tokens to every session and 2,220 once invoked, about $0.0006 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…