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/hamsurang/kit/obsidiannpx skills add hamsurang/kit --skill obsidiangit clone --depth 1 https://github.com/hamsurang/kitWhat 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.00184 | $0.01445 |
| Opus 5 | $0.00092 | $0.00723 |
| Sonnet 5 | $0.00037 | $0.00289 |
| Haiku 4.5 | $0.00018 | $0.00145 |
Grade A, and why
obsidian 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 2d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian Vault Skill
Contents
- Tool Selection Guide
- Find the Vault
- Working with Notes
- Multi-Vault Usage
- Common Patterns
- When NOT to Use
- Error Handling
- Obsidian Headless
- CLI Reference
Obsidian vault = a normal folder of Markdown files on disk. Use obsidian-cli only when its features add real value (search, link-aware move/rename, frontmatter ops, opening in Obsidian).
Tool Selection Guide
| Task | Best tool |
|---|---|
| Read note content | Read tool |
| Edit note content | Edit tool |
| Create new note | Write tool |
| Create note + open in Obsidian | obsidian-cli create --open |
| Search note names | obsidian-cli search "query" |
| Search inside notes | obsidian-cli search-content "query" |
| Broad content search / regex | Grep tool on vault path |
| Find notes by name pattern | Glob tool on vault path |
| Move/rename note (updates wikilinks) | obsidian-cli move |
| View/edit frontmatter | obsidian-cli frontmatter |
| Open daily note | obsidian-cli daily |
| List vault contents | obsidian-cli list |
| Delete note | obsidian-cli delete |
| Sync vault (no desktop) | ob sync |
Find the Vault
Never hardcode paths. Resolve the vault path first:
obsidian-cli print-default --path-only # if default vault is set
cat ~/Library/Application\ Support/obsidian/obsidian.json # otherwise
The config JSON has a vaults object; use the entry with "open": true. If multiple vaults exist, ask the user which to use, then: obsidian-cli set-default "<vault-folder-name>"
Working with Notes
Read: Use Read tool on the .md file directly. For backlink context: obsidian-cli print "Note" --mentions
Create: Use Write tool for simple creation. To also open in Obsidian: obsidian-cli create "Folder/Note" --content "..." --open. To append: add --append.
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.
- 2d ago First seen · 139 lines · 184 tokens per session scan A 7d5249c2dfe2
obsidian is a skill published in the GitHub repository hamsurang/kit (19 stars, last pushed 4mo ago), licensed MIT. It adds 184 tokens to every session and 1,445 once invoked, about $0.0009 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…