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 SikJa/hermes-obsidian-setup-consultant --skill obsidian-setup-consultantgit clone --depth 1 https://github.com/SikJa/hermes-obsidian-setup-consultantWrote 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/sikja/hermes-obsidian-setup-consultant/obsidian-setup-consultant)<a href="https://agentmods.dev/skills/sikja/hermes-obsidian-setup-consultant/obsidian-setup-consultant"><img src="https://agentmods.dev/badge/skills/sikja/hermes-obsidian-setup-consultant/obsidian-setup-consultant/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/sikja/hermes-obsidian-setup-consultant/obsidian-setup-consultant"><img src="https://agentmods.dev/badge/skills/sikja/hermes-obsidian-setup-consultant/obsidian-setup-consultant.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.00124 | $0.01844 |
| Opus 5 | $0.00062 | $0.00922 |
| Sonnet 5 | $0.00025 | $0.00369 |
| Haiku 4.5 | $0.00012 | $0.00184 |
Grade A, and why
obsidian-setup-consultant 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian Setup Consultant
Use this skill to guide someone from zero to a usable Obsidian vault that can work as a second brain, project memory, research base, or agent-readable knowledge system.
The goal is not to create the most complex Obsidian possible. The goal is to make a vault the user will actually use, with a clear capture flow, stable folders, and a structure that future AI agents can read without guessing.
Core principle
Obsidian is a folder of Markdown files. That makes it ideal for humans and agents:
- Humans use Obsidian to browse, link, write, graph, clip and review.
- Agents such as Hermes can use filesystem tools to search, read, create, patch and organize notes.
- Cloud/sync is optional; it only decides where the folder lives and how devices share it.
Start with 10 questions
Before proposing structure or plugins, ask these questions and wait for answers:
- What do you want to use Obsidian for mainly: business, study, projects, writing, personal life, research, AI agents, or a mix?
- What information will you save most often: notes, PDFs, links, videos, transcripts, audios, ideas, tasks, clients, code, or documentation?
- Do you want a simple folder structure or a more complete personal operating system?
- Will you use it on one computer, multiple computers, or also on mobile?
- Which sync/cloud option do you prefer or already use: Obsidian Sync, iCloud, Google Drive, OneDrive, Dropbox, Git, Syncthing, or local only?
- Do you want Hermes or another AI agent to read, search, create and edit notes in the vault?
- What 3–7 big areas of life/work should exist from day one?
- Do you want to preserve full sources separately from processed summaries?
- Which plugin categories matter: navigation, Web Clipper, Canvas, Excalidraw, graph, calendar, tasks, Dataview, templates, or minimalism?
- What is one real thing you will capture tomorrow, and how would you want to find it later?
If the user already provided some answers, only ask for the missing ones. Do not force all 10 again if the context is clear.
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 · 228 lines · 124 tokens per session scan A f171ff475d53
obsidian-setup-consultant is a skill published in the GitHub repository SikJa/hermes-obsidian-setup-consultant (2 stars, last pushed 3mo ago), licensed MIT. It adds 124 tokens to every session and 1,844 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
wiki-switch
Switch between multiple Obsidian wiki vault profiles. Use this skill when the user says "/wiki-switch NAME", "switch to my work wiki", "switch vault", "change wiki", "which wiki am I on", "list my wikis", "show my vaults", "create a new vault config", or "add a new wiki profile". The skill manages named config files…
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
knowledge-base-management
A lifecycle system for managing an Obsidian knowledge base, which is a folder of linked notes. It organizes raw material, AI-maintained wiki pages, and generated views into separate layers.
link-memory
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.
link-retrieve
Use before answering work that may depend on user memory, project history, source-backed notes, or prior decisions; retrieve compact Link context through the CLI without loading the whole wiki or requiring MCP.
link-ingest
Use when raw files are present, source pages look stale, or a user asks to ingest notes into Link; refresh source-backed wiki pages, propose memories, and validate updates through the CLI without MCP.