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 arozumenko/sdlc-skills --skill obsidian-vaultgit clone --depth 1 https://github.com/arozumenko/sdlc-skillsWrote 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/arozumenko/sdlc-skills/obsidian-vault)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/obsidian-vault"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/obsidian-vault/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/arozumenko/sdlc-skills/obsidian-vault"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/obsidian-vault.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00076 | $0.02625 |
| Opus 5 | $0.00038 | $0.01313 |
| Sonnet 5 | $0.00015 | $0.00525 |
| Haiku 4.5 | $0.00008 | $0.00263 |
Grade A, and why
obsidian-vault 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 11d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian Vault
Operate the user's Obsidian vault as a queryable second-brain — headlessly. The vault is plain markdown plus YAML frontmatter; the agent reads and writes files directly. Obsidian itself is for the user to browse the result later.
This skill is self-contained and stdlib-only. It pairs well with an agent-internal memory skill (e.g. the memory skill), but doesn't require one:
| Where | What goes here | Who reads it |
|---|---|---|
| Agent memory (if any) | Short-lived cognition, operational logs | The agent |
$OBSIDIAN_VAULT_PATH/ |
User-facing knowledge base, signals, contacts | The user (in Obsidian); agent files into it |
If unsure where something belongs: short-lived agent thought → memory; user might want to read it later → vault.
The CLI is scripts/vault.py. Vault path comes from $OBSIDIAN_VAULT_PATH or --vault; the CLI exits with an error if neither is set. Output is human-readable on stdout; errors → stderr; non-zero exit on failure.
Vault layout
The skill enforces this layout for any note it creates. Existing notes are not migrated.
<vault>/
inbox/ # raw, unprocessed signals — landing zone
daily/YYYY-MM-DD.md # user-facing daily note (append-only)
people/ # one note per contact — the leverage folder
projects/ # active projects
researches/ # deep-dive notes, reading captures
meetings/ # synchronous events with attendees + outcomes
decisions/ # decision log — "why did we do X"
memories/ # user-facing long-term memories
mails/ # processed email archive
chats/ # processed chat snippets (Telegram, Teams, Slack)
plans/ # plans, roadmaps, intent docs
attachments/ # binaries (images, PDFs, audio)
templates/ # frontmatter templates per note type
open-loops.md # active follow-ups (single flat file)
open-loops-archive/
YYYY-MM.md # one file per month, closed loops
What ships with it
18 files 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.
- README.md 1.5 KB
- scripts/vault.py 36 KB runs code
- templates/bases/active-projects.base 232 B
- templates/bases/inbox.base 190 B
- templates/bases/open-loops.base 92 B
- templates/bases/people-by-recency.base 209 B
- templates/bases/recent-meetings.base 266 B
- templates/chat.md 208 B
- templates/daily.md 90 B
- templates/decision.md 232 B
- templates/mail.md 211 B
- templates/meeting.md 190 B
- templates/memory.md 88 B
- templates/person.md 198 B
- templates/plan.md 129 B
- templates/project.md 198 B
- templates/research.md 151 B
- templates/signal.md 168 B
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.
- 11d ago First seen · 241 lines · 76 tokens per session scan A aa3c6fe08fa4
obsidian-vault is a skill published in the GitHub repository arozumenko/sdlc-skills (20 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 2,625 once invoked, about $0.0004 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.