Borrowing it
Nothing to install: this file belongs to future-architect/uzomuzo-oss. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/future-architect/uzomuzo-oss/main/.github/prompts/batch-issues.prompt.mdgit clone --depth 1 https://github.com/future-architect/uzomuzo-ossWrote 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/commands/future-architect/uzomuzo-oss/batch-issues)<a href="https://agentmods.dev/commands/future-architect/uzomuzo-oss/batch-issues"><img src="https://agentmods.dev/badge/commands/future-architect/uzomuzo-oss/batch-issues/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/commands/future-architect/uzomuzo-oss/batch-issues"><img src="https://agentmods.dev/badge/commands/future-architect/uzomuzo-oss/batch-issues.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.00024 | $0.02446 |
| Opus 5.5 | $0.00010 | $0.00978 |
| Sonnet 5.5 | $0.00005 | $0.00489 |
| Haiku 4.5 | $0.00002 | $0.00245 |
Grade A, and why
batch-issues 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/batch-issues -- Parallel Issue Dispatcher
You are orchestrating parallel resolution of multiple GitHub issues using isolated Agent workers. Each worker runs in its own worktree to prevent branch conflicts.
Arguments
Parse the user's arguments:
- No arguments: Auto-select small/medium open issues, analyze conflicts, dispatch
<issue numbers>: Process specific issues (e.g.,/batch-issues 168 171 187)--dry-run: Analyze and show the dispatch plan without launching agents--max-parallel N: Maximum parallel agents (default: 4)
Procedure
Phase 1: Issue Selection
- Run
gh issue list --state open --limit 30 --json number,title,labels,body - Exclude meta-issues (Dependency Dashboard, release checklists, scan reports)
- Exclude issues labeled
documentation(unless explicitly requested) - If specific issue numbers were provided, use those; otherwise auto-select
Phase 2: Conflict Analysis
For each candidate issue:
- Read the issue body to identify which files/packages it likely touches
- Search the codebase (
grep,Glob) to confirm file targets - Build a conflict matrix: issues that modify the same files cannot run in parallel
Group issues into conflict groups:
- Issues sharing files go in the same group (run sequentially within group)
- Issues with no shared files are independent (run in parallel across groups)
Phase 3: Size & Risk Assessment
For each issue, classify:
- Small: Single function fix, test addition, output formatting (< 50 lines changed)
- Medium: Multi-function fix, new test file, query changes (50-200 lines)
- Large: Cross-cutting refactor, new feature, architectural change (> 200 lines)
- Exclude: Issues requiring design decisions, user input, or external dependencies
Exclude Large issues unless explicitly requested. Present the plan to the user.
Phase 4: Dispatch Plan
Present the dispatch plan as a table:
| Batch | Issues | Conflict Group | Estimated Size |
|-------|--------|----------------|----------------|
| 1 | #168, #171, #187, #180 | independent | S, M, M, M |
| 2 | #181 (after #171), #186 (after #187) | C, A | M, M |
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 · 256 lines · 24 tokens per session scan A 9f91d12ed642
batch-issues is a command published in the GitHub repository future-architect/uzomuzo-oss (42 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 2,446 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-09-07.
Other commands, from other repositories
revisit
Intake recorded each item below as blocked: something had to happen first. Work lands in parallel, so a blocker can be resolved, superseded or made irrelevant while its issue is still open, and an item can stay blocked long after it could move. Judge, for each item, whether it still looks blocked now. You don't…
create-issue
Create a GitHub issue with proper template discovery and population.
next
Suggest the most likely next workflow action based on current context.
aft
Transfer feature from its current agent to a different agent — preserves commits and in-flight work (shortcut for feature-transfer).
afs
Start feature [agents...] - create workspace and begin implementation (shortcut for feature-start).
aigon-feature-transfer
Hand a stuck or paywalled in-progress feature from its current agent to a different agent, without losing commits or in-flight work. Intended for.