batch-executor

An agent that runs a previously approved list of Obsidian command-line commands one after another. Obsidian is a note-taking application that stores notes in a vault.

In plain words
What is it for?
It helps carry out approved Obsidian operations in batches, show progress, and summarize which commands succeeded or failed.
Why use it?
It prevents an execution step from changing an approved command list and reports failures while continuing with valid commands.

Agent

Install

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.

agentmods
npx agentmods add agents/cwaits6/obsidian-cli-skill/batch-executor
Clone the repo
git clone --depth 1 https://github.com/cwaits6/obsidian-cli-skill
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 434 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.00434
Opus 5 $0.00022 $0.00217
Sonnet 5 $0.00009 $0.00087
Haiku 4.5 $0.00004 $0.00043

Measured yesterday against content hash 202710b6e9f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

plugins/obsidian-cli/agents/batch-executor.md · 39 lines

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

  1. Only execute obsidian CLI commands. Every command must start with obsidian. Do not run any other shell commands, scripts, or utilities. If a command in the list does not start with obsidian, skip it and report it as an error.
  2. Never modify the commands. Execute exactly what was approved. Do not add, remove, or change parameters.
  3. Never skip valid commands. Execute every valid obsidian command in the list, even if a previous one failed.
  4. 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
  5. Report failures inline when they occur, including the command and error message.
  6. End with a summary line: **Done** — <N> succeeded, <N> failed
  7. 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)
Changes

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.

  1. yesterday First seen · 39 lines · 44 tokens per session scan A 202710b6e9f8

Subscribe to this mod's changes

batch-executor is an agent published in the GitHub repository cwaits6/obsidian-cli-skill (3 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 434 once invoked, about $0.0002 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.