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 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/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/cwaits6/obsidian-cli-skill/obsidian-cli"><img src="https://agentmods.dev/badge/skills/cwaits6/obsidian-cli-skill/obsidian-cli.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.00258 | $0.01652 |
| Opus 5.5 | $0.00103 | $0.00661 |
| Sonnet 5.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 2mo 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.
- 2mo 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 7mo ago), licensed MIT. It adds 258 tokens to every session and 1,652 once invoked, about $0.0010 per session on Opus 5.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
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
recall
Recall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.
assigns-audit
Inspect LiveView socket assigns for memory bloat — missing temporaryassigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporaryassigns.
compound-docs
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
evolving-status
View Self-Evolving Loop session status, history, and memory metrics.
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…