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/cwaits6/obsidian-cli-skill/obsidian-clinpx skills add cwaits6/obsidian-cli-skill --skill obsidian-cligit clone --depth 1 https://github.com/cwaits6/obsidian-cli-skillWrote 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/cwaits6/obsidian-cli-skill/obsidian-cli)<a href="https://agentmods.dev/skills/cwaits6/obsidian-cli-skill/obsidian-cli"><img src="https://agentmods.dev/badge/skills/cwaits6/obsidian-cli-skill/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.00258 | $0.01652 |
| Opus 5 | $0.00129 | $0.00826 |
| Sonnet 5 | $0.00052 | $0.00330 |
| Haiku 4.5 | $0.00026 | $0.00165 |
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 3d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian CLI Skill
Batch automation of your Obsidian vault using the Obsidian CLI. Analyzes notes, assigns properties based on content, and orchestrates migrations, base creation, template generation, and other vault operations.
Instructions
-
Read config first. Before any operation that depends on property schema, batch settings, or vault preferences, read the user's config:
~/.claude/plugins/marketplaces/obsidian-cli-skill/plugins/obsidian-cli/config.yamlIf
config.yamldoes not exist, fall back toconfig.yaml.examplein the same directory. -
Always consult reference files before constructing any command. Never guess syntax, parameter names, or examples. Commands use
param=valueparameters plus bare flags (total,verbose,silent). Avoid GNU-style--flagsyntax except where Obsidian explicitly documents it as global behavior. Use the command routing table below to find the right reference. -
Propose before executing. Present changes for user review and get explicit approval before modifying any files. Follow output-format-standard.md for all output formatting.
-
If a command isn't in the references, it may not exist. Consider native Obsidian workflows instead — see native-workflows.md.
Workflow
All operations follow this pattern:
- Analyze — Read notes/requirements and config.yaml
- Propose — Present changes for review (follow output format standard)
- Approve — User reviews and approves before any files are modified
- Execute — Run approved operations via Obsidian CLI
Approval mode is controlled by batch_settings.approval_mode in config.yaml:
batch— Approve the entire phase at once, then all operations execute without further promptssingle— Approve each note individually before proceeding
Batch splitting: If notes exceed batch_settings.max_batch_size, split into multiple batches — propose and get approval for each batch separately.
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.
- 3d ago First seen · 105 lines · 258 tokens per session scan A 773b6927f532
obsidian-cli is a skill published in the GitHub repository cwaits6/obsidian-cli-skill (3 stars, last pushed 5mo ago), licensed MIT. It adds 258 tokens to every session and 1,652 once invoked, about $0.0013 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
code-reviewer
Code review knowledge base: quality, security (OWASP Top 10), error-handling, performance, and test-coverage checklists with severity-ranked output format. Use when reviewing code changes, PRs, or before commits. Loaded automatically by the code-reviewer agent.
evolving-status
View Self-Evolving Loop session status, history, and memory metrics.
superbrain-distill
Internal SuperBrain skill — run by the detached capture child to distill a session-event delta into routed Obsidian notes. Not for direct user invocation.
orient
Use when user invokes /orient with a topic keyword, entity type, project name, time qualifier, or combination. Also triggers on "what do we know about X", "remind me about X", "where did we leave off on X". Provides targeted context loading — searches the MCP Memory Server graph, knowledge files, journal entries, and…
memory
Use when user invokes /memory with a subcommand (search, trace, add, episode, status). Also triggers on "search my memory for X", "add to memory", "what do I know about X" (when membrain is available), "memory status", "memory trace". Searches and manages the membrain knowledge graph via MCP tools or HTTP API.
garden-tending
Tend the knowledge garden — diagnose vault health, condense project memos into project.md overviews, create/merge cross-project topics, fix broken links, archive superseded notes, extend trails. Trigger on "tend the garden", "condense", "update project overview", "check vault health", "where are we with X?", "what…