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 agentmods add skills/future-architect/uzomuzo-oss/batch-issuesnpx skills add future-architect/uzomuzo-oss --skill batch-issuesgit 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/skills/future-architect/uzomuzo-oss/batch-issues)<a href="https://agentmods.dev/skills/future-architect/uzomuzo-oss/batch-issues"><img src="https://agentmods.dev/badge/skills/future-architect/uzomuzo-oss/batch-issues.svg" alt="Measured on agentmods" 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 | $0.00049 | $0.00436 |
| Opus 5 | $0.00024 | $0.00218 |
| Sonnet 5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00044 |
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 3d 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
/batch-issues -- Parallel Issue Dispatcher
Full specification: See
.github/prompts/batch-issues.prompt.mdfor the complete procedure, conflict analysis, agent workflow, and safety rules.
Quick Reference
- Auto-select:
/batch-issues-- pick open issues, analyze conflicts, dispatch - Specific issues:
/batch-issues 168 171 187-- process these issues - Dry run:
/batch-issues --dry-run-- show plan only - Limit parallelism:
/batch-issues --max-parallel 2 - Phase 1: Issue selection & filtering
- Phase 2: Conflict analysis (shared file detection)
- Phase 3: Size/risk assessment (S/M/L classification)
- Phase 4: Dispatch plan (present to user)
- Phase 5: Agent dispatch (worktree-isolated, parallel across groups, sequential within)
- Phase 6: Summary report with PR links
- Phase 6.5: Orchestrator review — run
/review-until-cleanon each PR (agents can't launch independent reviewers) - Phase 7: Evidence verification — check/fix Before/After test output in every PR body
- Each agent: reproduce (MANDATORY) -> architect -> implement -> self-check -> verify after (MANDATORY) -> before/after PR (template enforced)
- Independent review runs at orchestrator level (Phase 6.5), NOT inside agents
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.
- 3d ago First seen · 33 lines · 49 tokens per session scan A 9d2df2e17025
batch-issues is a skill published in the GitHub repository future-architect/uzomuzo-oss (32 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 436 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-09-01.
Other skills, from other repositories
papercut
Capture or triage small Neva repository and engineering-harness frictions without derailing feature work.
skip-test-with-issue
Skip a flaky or broken test with proper issue tracking. Use when asked to skip a test, disable a test, or mark a test as flaky.
kanban-md
Manage project tasks using kanban-md, a file-based kanban board CLI. Use when the user mentions tasks, kanban, board, backlog, sprint, project management, work items, priorities, blockers, or wants to track, create, list, move, edit, or delete tasks. Also use for standup, status update, sprint planning, triage, or…
kanban-based-development
Autonomous, parallel-safe development workflow using kanban-md. Use when the user asks to work through tasks, do kanban-based development, or when multiple agents need to coordinate work on the same codebase. Optimized for explicit handoffs and a "defer to user" protocol when human intervention is required.
clickup-cli
ClickUp CLI for managing tasks, sprints, comments, statuses, Docs, and archiving. Use when the user needs to interact with ClickUp — creating/editing/archiving tasks, checking sprint status, adding comments, linking PRs, managing Docs and pages, or searching tasks. Includes a generic clickup api passthrough covering…
miro-workflow
Compose Miro boards from natural-language requests by combining tools from miro-mcp-server. Use when the user asks to set up a sprint board, retrospective, brainstorming session, user story map, kanban, or any structured Miro layout. Do NOT use for single-tool calls (create one sticky), questions about Miro the…