A command for writing multiple operations work plans in one uninterrupted run. It creates a separate plan for each supplied task and saves questions for discussion afterward.

Use it for research, content, specifications, briefs, and other non-code tasks. It does not plan changes to application code.

It avoids stopping between plans for clarification and keeps a large batch of non-code planning work organized.

batch-plan — Command for Claude Code by OdinMB/ops-workflow

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.

Clone the repo

git clone --depth 1 https://github.com/OdinMB/ops-workflow

Made for: Claude Code.

Or install ops, the plugin that ships this one along with the rest of its 9 skills, 10 commands, 5 agents.

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

README.md

[![agentmods](https://agentmods.dev/badge/commands/odinmb/ops-workflow/batch-plan/github.svg)](https://agentmods.dev/commands/odinmb/ops-workflow/batch-plan)

Your own site

<a href="https://agentmods.dev/commands/odinmb/ops-workflow/batch-plan"><img src="https://agentmods.dev/badge/commands/odinmb/ops-workflow/batch-plan/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/odinmb/ops-workflow/batch-plan"><img src="https://agentmods.dev/badge/commands/odinmb/ops-workflow/batch-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 884 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00028	$0.00884
Opus 5.5	$0.00011	$0.00354
Sonnet 5.5	$0.00006	$0.00177
Haiku 4.5	$0.00003	$0.00088

Measured 9d ago against content hash ca547600168a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

batch-plan 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 9d 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.

commands/batch-plan.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Task

You will be going on a plan writing spree for non-code work. I will provide a list of tasks or ideas. Write an ops plan for each of these items without interruptions.

Follow the ops:work-autonomously skill throughout.

Guidelines

Create a follow-up file per the ops:work-autonomously skill.
At the start of the batch, pick a short slug-style batch prefix that names the theme of this batch (e.g. music, q2-launch, donor-outreach). Use the user's framing if they offered one; otherwise derive it from the tasks. Keep it lowercase, hyphenated, and brief.
Filenames of plans should reference the goal of the plan, with today's date and the batch+order prefix: <batch>-<NN>-YYYY-MM-DD-<slug>.md (e.g. music-01-2026-04-19-launch-brief.md). The batch prefix keeps multiple concurrent ordered batches in plans/ from stepping on each other.
You can write plans in parallel if they don't directly relate to each other.
Scope check: Plans must never include implementing changes in app codebases. This workflow produces content, research, specs, and briefs — not code. If the repo's CLAUDE.md has an ## Autopilot section, a plan for code or product work also ends with an entry in backlog/ideas.md linking its spec, so autopilot routes it to a repository and weighs it against the charter.

Triage

Before planning, classify each task as trivial or needs-plan:

Trivial — a single obvious deliverable with no open questions: a small content edit, a one-paragraph note, updating a single field in a tracker, pasting known information into a document, a short email draft. No research required, no structural decisions, no stakeholder calls to resolve.
Needs-plan — everything else: multi-step work, research, content requiring judgment, anything with open questions a planner could usefully surface.

When in doubt, treat it as needs-plan.

Trivial tasks skip the planner entirely and go into a single plans/<batch>-direct-tasks.md file as numbered entries. Non-trivial tasks get planned as usual. Use the same numeric prefix sequence for both so execution order across the whole batch is preserved. With batch prefix music:

Read the full file on GitHub · 64 lines

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.

9d ago Changed ca547600168a
10d ago Changed 19230ee24b1a
11d ago Changed · -2 lines · -14 tokens per session 727348af7493
2mo ago First seen · 66 lines · 42 tokens per session scan A 44afc6feecdb

Subscribe to this mod's changes

batch-plan is a command published in the GitHub repository OdinMB/ops-workflow (6 stars, last pushed 10d ago), licensed MIT. It adds 28 tokens to every session and 884 once invoked, about $0.0001 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.

Autonomous Agents Claude Code Planning ai-workflows claude-code-agents claude-code-config claude-code-skills

batch-plan next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
batch-planOdinMB/ops-workflow	Command	6	10d ago	MIT	A	28	Claude Code
forge-compact-taskluiseiman/dotforge	Command	8	2d ago	MIT	A	46	Claude Code
forge-bootstrapluiseiman/dotforge	Command	8	2d ago	MIT	A	20	Claude Code
forge-insightsluiseiman/dotforge	Command	8	2d ago	MIT	A	16	Claude Code
capluiseiman/dotforge	Command	8	2d ago	MIT	A	19	Claude Code
forge-auditluiseiman/dotforge	Command	8	2d ago	MIT	A	17	Claude Code
forge-captureluiseiman/dotforge	Command	8	2d ago	MIT	A	20	Claude Code