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 bravew/trove --skill trove-obsidian-cligit clone --depth 1 https://github.com/bravew/troveWrote 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/bravew/trove/trove-obsidian-cli)<a href="https://agentmods.dev/skills/bravew/trove/trove-obsidian-cli"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-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/bravew/trove/trove-obsidian-cli"><img src="https://agentmods.dev/badge/skills/bravew/trove/trove-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.00052 | $0.01036 |
| Opus 5.5 | $0.00021 | $0.00414 |
| Sonnet 5.5 | $0.00010 | $0.00207 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
trove-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 1mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian CLI
Use the installed CLI's help as the command contract. Obsidian desktop must support and enable the CLI; invoking it can start the app if it is closed. Do not assume that a generic notes directory is an Obsidian vault.
Establish capabilities and targets
- Check executable availability, for example
command -v obsidianon POSIX orGet-Command obsidianon PowerShell. If unavailable, use filesystem tools for authorized file work when the vault path is known. Explain the limit for app-only operations. Do not install or configure software silently. - Read
obsidian helpandobsidian help <command>for the operation. The examples below are patterns to verify, not a substitute for installed help. - Resolve the vault name or ID and the exact target from the request and
available context. Use
vault=<name-or-id>before the command. Use a vault-relativepath=<path>for files.file=<name>can be ambiguous. If an unresolved choice could edit the wrong vault or note, ask for that target before the dependent write; continue independent read-only work. - Read the target before changing it. Do not rely on the active file or focused vault as an implicit write destination.
Command patterns
Parameters use key=value; boolean flags have no value. POSIX examples use
single quotes so shell substitutions remain literal. Adapt quoting to the
actual shell and pass an argument array through tools that support it.
obsidian help search
obsidian vault='Work' search query='onboarding' limit=10
obsidian vault='Work' read path='Projects/Launch.md'
obsidian vault='Work' backlinks path='Projects/Launch.md'
After the user requests the corresponding change and the target is resolved:
obsidian vault='Work' append path='Projects/Launch.md' content='Review scheduled.'
obsidian vault='Work' property:set path='Projects/Launch.md' name='status' value='done'
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.
- 1mo ago First seen · 94 lines · 52 tokens per session scan A e95a5ce158ea
trove-obsidian-cli is a skill published in the GitHub repository bravew/trove (10 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,036 once invoked, about $0.0002 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-09-11.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
gog
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
box
Box manages cloud files, sharing, search, and metadata.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
recipe-save-email-attachments
Find Gmail messages with attachments and save them to a Google Drive folder.
material-organizer
Organize only the materials the user has already provided or explicitly pointed to. The job is to make messy inputs easier to scan, reuse, archive, or continue from later while preserving source traceability.