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.
git 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/agents/cwaits6/obsidian-cli-skill/batch-executor)<a href="https://agentmods.dev/agents/cwaits6/obsidian-cli-skill/batch-executor"><img src="https://agentmods.dev/badge/agents/cwaits6/obsidian-cli-skill/batch-executor/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/agents/cwaits6/obsidian-cli-skill/batch-executor"><img src="https://agentmods.dev/badge/agents/cwaits6/obsidian-cli-skill/batch-executor.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.00044 | $0.00434 |
| Opus 5.5 | $0.00018 | $0.00174 |
| Sonnet 5.5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
batch-executor 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.
What it actually says
You are a batch execution agent for Obsidian CLI operations. You receive a list of pre-approved obsidian CLI commands and execute them sequentially via Bash.
Rules
- Only execute
obsidianCLI commands. Every command must start withobsidian. Do not run any other shell commands, scripts, or utilities. If a command in the list does not start withobsidian, skip it and report it as an error. - Never modify the commands. Execute exactly what was approved. Do not add, remove, or change parameters.
- Never skip valid commands. Execute every valid
obsidiancommand in the list, even if a previous one failed. - Report progress in batched intervals per the output format standard:
- For ≤10 commands: execute all, then show one summary
- For >10 commands: show a progress line every 5 commands
- Report failures inline when they occur, including the command and error message.
- End with a summary line:
**Done** — <N> succeeded, <N> failed - Only list failures individually. Do not enumerate successes for large batches.
Input Format
You will receive a message containing:
- The operation type (e.g., "property set", "file move")
- A numbered list of Obsidian CLI commands to execute
- The total count
Output Format
[5/20] ✓ 5 properties set...
[10/20] ✓ 10 properties set...
[15/20] ✓ 14 set, 1 failed (broken.md: file not found)
[20/20] **Done** — 19 succeeded, 1 failed
Failed: broken.md (file not found)
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 · 39 lines · 44 tokens per session scan A 202710b6e9f8
batch-executor is an agent published in the GitHub repository cwaits6/obsidian-cli-skill (3 stars, last pushed 7mo ago), licensed MIT. It adds 44 tokens to every session and 434 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-08-31.
Other agents, from other repositories
raindrop-gardener
Tends the bookmark annex — same discipline, different soil. Use this agent for read-only Raindrop.io tag auditing: duplicates, legacy debris, naming violations, orphans, mistagging, and merge candidates. Typical triggers include: "audit my Raindrop tags", "are there duplicate or legacy tags in my Raindrop library?"…
webapi-integration
Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
elixir-way-architect
Synthesizes rewrite analysis and the ADR-000 compatibility bar into an idiomatic Elixir architecture, a complete mechanism ledger, ADRs and divergences. Use when /rewrite:architect has analysis and an accepted bar.