New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Batch

by asgeirtj in asgeirtj/system_prompts_leaks

Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.

CC0-1.0Auto-check passedDevelopment

Install Batch

skills CLI
$ npx skills add asgeirtj/system_prompts_leaks --skill batch -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install asgeirtj/system_prompts_leaks batch --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Anthropic/claude-code/skills/batch .claude/skills/batch && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
batch
GitHub stars
69k
Token cost
~1.3k tokens
SKILL.md length
601 words
Files
1
Skills in repo
121
Repo updated
First seen
Licence
CC0-1.0

At a glance

Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.

  • Works in 3 steps: Research and Plan (Plan Mode) → Spawn Workers (After Plan Approval) → Track Progress
  • Tasks that involve Pull requests
  • SKILL.md covers User Instruction, Phase 1: Research and Plan…, Phase 2: Spawn Workers (After… and Phase 3: Track Progress
  • Calls bun

What it does

Batch is an agent skill from asgeirtj/system_prompts_leaks. Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests and Git worktrees. The repository describes itself as: Documented system prompts from Anthropic - Claude Fable 5.1, Opus 5.5, Claude Design, Claude Code. OpenAI - ChatGPT GPT-6-Astra, Codex. Google - Gemini 3.8 Flash, 3.1 Pro… The licence is CC0-1.0.

When your agent uses it

  • Tasks that involve Pull requests
  • Tasks that involve Git worktrees

Example prompts

  • “/batch”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Research and Plan (Plan Mode)
  2. Spawn Workers (After Plan Approval)
  3. Track Progress

What it can do on your machine

Read from SKILL.md and the folder at commit dd45aa5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bun

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Batch loads about 1.3k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 601 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from asgeirtj/system_prompts_leaks at commit dd45aa5, republished under its CC0-1.0 licence (© asgeirtj). 601 words, ~1,328 tokens.

Download SKILL.mdSave it as .claude/skills/batch/SKILL.md (or your agent's skills folder).
name
batch
description
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
when_to_use
Use when the user wants to make a sweeping, mechanical change across many files (migrations, refactors, bulk renames) that can be decomposed into independent…
disable-model-invocation
true

Batch: Parallel Work Orchestration

You are orchestrating a large, parallelizable change across this codebase.

User Instruction

$ARGUMENTS

Phase 1: Research and Plan (Plan Mode)

Call the EnterPlanMode tool now to enter plan mode, then:

  1. Understand the scope. Launch one or more subagents (in the foreground — you need their results) to deeply research what this instruction touches. Find all the files, patterns, and call sites that need to change. Understand the existing conventions so the migration is consistent.

  2. Decompose into independent units. Break the work into 5–30 self-contained units. Each unit must:

    • Be independently implementable in an isolated git worktree (no shared state with sibling units)
    • Be mergeable on its own without depending on another unit's PR landing first
    • Be roughly uniform in size (split large units, merge trivial ones)

    Scale the count to the actual work: few files → closer to 5; hundreds of files → closer to 30. Prefer per-directory or per-module slicing over arbitrary file lists.

  3. Determine the e2e test recipe. Figure out how a worker can verify its change actually works end-to-end — not just that unit tests pass. Look for:

    • A claude-in-chrome skill or browser-automation tool (for UI changes: click through the affected flow, screenshot the result)
    • A tmux or CLI-verifier skill (for CLI changes: launch the app interactively, exercise the changed behavior)
    • A dev-server + curl pattern (for API changes: start the server, hit the affected endpoints)
    • An existing e2e/integration test suite the worker can run

    If you cannot find a concrete e2e path, use the AskUserQuestion tool to ask the user how to verify this change end-to-end. Offer 2–3 specific options based on what you found (e.g., "Screenshot via chrome extension", "Run bun run dev and curl the endpoint", "No e2e — unit tests are sufficient"). Do not skip this — the workers cannot ask the user themselves.

    Write the recipe as a short, concrete set of steps that a worker can execute autonomously. Include any setup (start a dev server, build first) and the exact command/interaction to verify.

  4. Write the plan. In your plan file, include:

    • A summary of what you found during research
    • A numbered list of work units — for each: a short title, the list of files/directories it covers, and a one-line description of the change
    • The e2e test recipe (or "skip e2e because …" if the user chose that)
    • The exact worker instructions you will give each agent (the shared template)

  5. Call ExitPlanMode to present the plan for approval.

Show full SKILL.md (194 more words)Show less

Phase 2: Spawn Workers (After Plan Approval)

Once the plan is approved, spawn one background agent per work unit using the Agent tool. All agents must use isolation: "worktree" and run_in_background: true. Launch them all in a single message block so they run in parallel.

For each agent, the prompt must be fully self-contained. Include:

  • The overall goal (the user's instruction)
  • This unit's specific task (title, file list, change description — copied verbatim from your plan)
  • Any codebase conventions you discovered that the worker needs to follow
  • The e2e test recipe from your plan (or "skip e2e because …")
  • The worker instructions below, copied verbatim:
After you finish implementing the change:
1. **Code review** — Invoke the `Skill` tool with `skill: "code-review"` to find correctness bugs (it reports findings; it does not edit code). Fix any findings it surfaces before continuing.
2. **Run unit tests** — Run the project's test suite (check for package.json scripts, Makefile targets, or common commands like `npm test`, `bun test`, `pytest`, `go test`). If tests fail, fix them.
3. **Test end-to-end** — Follow the e2e test recipe from the coordinator's prompt (below). If the recipe says to skip e2e for this unit, skip it.
4. **Commit and push** — Commit all changes with a clear message, push the branch, and create a PR with `gh pr create`. Use a descriptive title. If `gh` is not available or the push fails, note it in your final message.
5. **Report** — End with a single line: `PR: <url>` so the coordinator can track it. If no PR was created, end with `PR: none — <reason>`.

Use subagent_type: "general-purpose" unless a more specific agent type fits.

Phase 3: Track Progress

After launching all workers, render an initial status table:

#UnitStatusPR
1<title>running—
2<title>running—

As background-agent completion notifications arrive, parse the PR: <url> line from each agent's result and re-render the table with updated status (done / failed) and PR links. Keep a brief failure note for any agent that did not produce a PR.

When all agents have reported, render the final table and a one-line summary (e.g., "22/24 units landed as PRs").

© asgeirtj, CC0-1.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in Anthropic/claude-code/skills/batch of asgeirtj/system_prompts_leaks.

Open the folder on GitHubat commit dd45aa5

Compare with similar skills

Batch next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Batch compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Batch this skillasgeirtj/system_prompts_leaks69k—~1.3kAutomated safety check: PassCC0-1.0
Om Auto Continue PR Loopgo-musicfox/go-musicfox2.6k1 repos~5kAutomated safety check: NotesGPL-3.0
Work With PR Lifecyclecode-yeongyu/oh-my-openagent70k—~4.6kAutomated safety check: PassCustom licence
Branch Standup Facilitatorthedotmack/claude-mem98k—~1.7kAutomated safety check: NotesApache-2.0
Verify PRvfarcic/dot-agent-deck109—~7.3kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • Om Auto Continue PR Loop

    go-musicfox/go-musicfox

    Advanced om-auto-continue-pr for PRs started by om-auto-create-pr-loop — claims the PR, resumes from the first non-done PLAN.md Tasks row in an isolated worktree, keeps the per-step commit and…

    2.6k GitHub starsUsed in 1 repo~5k tokens
    DevelopmentAuto-check: notes

  • Work With PR Lifecycle

    code-yeongyu/oh-my-openagent

    Takes a task through to a merged pull request in an isolated git worktree, splitting it into small independent PRs and looping on CI and review gates until they pass.

    70k GitHub stars~4.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Branch Standup Facilitator

    thedotmack/claude-mem

    Facilitates a read-only standup between git worktrees, branches or PRs, where each acts as an agent in a shared markdown chat to agree one consolidation plan.

    98k GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Verify PR

    vfarcic/dot-agent-deck

    Deeply verify a pull request written by someone else and end with an explicit merge recommendation.

    109 GitHub stars~7.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from asgeirtj/system_prompts_leaks

All 121 skills in this repo

  • Fleet Manager for Agent Sessions

    asgeirtj/system_prompts_leaks

    Shows one digest of coding-agent sessions across your connected machines and lets you open, read, steer, approve, stop and close them, over Herdr, tmux or MSP.

    69k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Muse Code Product Doctor

    asgeirtj/system_prompts_leaks

    Diagnoses a Muse Code installation's own failures from binary and session evidence, instead of treating the report as an ordinary repository bug.

    69k GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Agents Project Coordinator

    asgeirtj/system_prompts_leaks

    Runs a goal as a project in which the agent coordinates separate agent threads, judging when to split the work, and interviews you first when nothing can be verified.

    69k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Muse Plugin Creator

    asgeirtj/system_prompts_leaks

    Creates and validates a new native Muse plugin package in the current workspace, limited to five capability families, and leaves installation to you.

    69k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Figma Design Inspector

    asgeirtj/system_prompts_leaks

    Inspects Figma designs through the figma CLI and Figma's MCP server to read variants, spacing, tokens and layouts and to extract assets for implementation.

    69k GitHub stars~936 tokensUpdated today
    Auto-check passed

  • Morning Brief Renderer

    asgeirtj/system_prompts_leaks

    Renders a calm, single-page HTML morning brief from your connected calendar, email and chat, or sets it up to run automatically on weekdays.

    69k GitHub stars~4.5k tokensUpdated today
    Auto-check passed

Categories

Questions about Batch

What does Batch do?

Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR. Batch is an agent skill from asgeirtj/system_prompts_leaks. Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.

When should I use Batch?

Batch fits situations like: tasks that involve Pull requests; tasks that involve Git worktrees.

How do I install Batch in Claude Code?

Run `npx skills add asgeirtj/system_prompts_leaks --skill batch -a claude-code`. Or copy the skill folder (Anthropic/claude-code/skills/batch in asgeirtj/system_prompts_leaks) into .claude/skills/batch in your project. Claude Code loads it when a task matches its description.

How do I install Batch in Codex?

Run `npx skills add asgeirtj/system_prompts_leaks --skill batch -a codex`. Or copy the skill folder (Anthropic/claude-code/skills/batch in asgeirtj/system_prompts_leaks) into .agents/skills/batch in your project. Codex loads it when a task matches its description.

Can I use Batch in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add asgeirtj/system_prompts_leaks --skill batch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/batch, .gemini/skills/batch, .github/skills/batch and .opencode/skills/batch in your project.

What does Batch need to run?

Going by SKILL.md and its folder, Batch needs the command-line tools its instructions call (bun).

Does Batch access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Batch safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Batch use?

Batch is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Batch use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Batch?

Skills that share tags, products or a category with Batch: Om Auto Continue PR Loop (go-musicfox/go-musicfox, 2.6k stars), Work With PR Lifecycle (code-yeongyu/oh-my-openagent, 70k stars), Branch Standup Facilitator (thedotmack/claude-mem, 98k stars) and Verify PR (vfarcic/dot-agent-deck, 109 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Batch?

asgeirtj (a GitHub user) maintains it in asgeirtj/system_prompts_leaks, which has 69,095 GitHub stars. The repository holds 121 skills in this directory. The repository was last updated on October 7, 2026.

Source: asgeirtj/system_prompts_leaks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.