work-batch

work-batch is a skill for Claude Code from christopherlouet/claude-base. It costs 47 tokens per session (733 once invoked), scanned A, original, MIT.

An autonomous workflow that reads user stories from a product-requirements file, implements them one by one, tests them, and commits the results.

In plain words
What is it for?
It helps process PRD files, apply test-driven development (writing tests before implementation), verify acceptance criteria, and create commits for completed stories.
Why use it?
It turns a backlog of defined tasks into a repeatable sequence, while stopping when a story’s tests fail.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter.

Good fit It helps process PRD files, apply test-driven development (writing tests before implementation), verify acceptance criteria, and create commits for completed stories.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/christopherlouet/claude-base/work-batch
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.

Any agent
npx skills add christopherlouet/claude-base --skill work-batch
Clone the repo
git clone --depth 1 https://github.com/christopherlouet/claude-base

Made for: Claude Code.

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.

agentmods badge for work-batch

README.md
[![agentmods](https://agentmods.dev/badge/skills/christopherlouet/claude-base/work-batch/github.svg)](https://agentmods.dev/skills/christopherlouet/claude-base/work-batch)
Your own site
<a href="https://agentmods.dev/skills/christopherlouet/claude-base/work-batch"><img src="https://agentmods.dev/badge/skills/christopherlouet/claude-base/work-batch/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.

agentmods 80×15 button for work-batch

Your own site · 80×15
<a href="https://agentmods.dev/skills/christopherlouet/claude-base/work-batch"><img src="https://agentmods.dev/badge/skills/christopherlouet/claude-base/work-batch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 733 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.00733
Opus 5.5 $0.00019 $0.00293
Sonnet 5.5 $0.00009 $0.00147
Haiku 4.5 $0.00005 $0.00073

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

Security

Grade A, and why

work-batch 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 25d 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.

.claude/skills/work-batch/SKILL.md · 110 lines

How it starts

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

Batch Execution Mode

Autonomous and sequential execution of user stories from a PRD file.

PRD file format

JSON (prd.json)

{
  "project": "project-name",
  "stories": [
    {
      "id": "US-001",
      "title": "Story title",
      "description": "Detailed description",
      "priority": "P1",
      "acceptance_criteria": [
        "Given X, When Y, Then Z"
      ],
      "files": ["src/module.ts", "src/module.test.ts"]
    }
  ]
}

Markdown (prd.md)

## US-001: Story title
**Priority**: P1
**Description**: Detailed description
**Acceptance criteria**:
- Given X, When Y, Then Z
**Files**: src/module.ts, src/module.test.ts

Workflow per story

For each story in priority order (P1 → P2 → P3):

1. LOAD - Load the story

  • Read the story from the PRD file
  • Display the title and description
  • Check prerequisites (files, dependencies)

2. IMPLEMENT - TDD cycle

  • Write the tests first (RED)
  • Implement the minimal code (GREEN)
  • Refactor if necessary (REFACTOR)
  • Verify the acceptance criteria

3. COMMIT - Save

  • Run the tests: npm test / pytest / go test
  • If tests OK: commit with feat(scope): US-XXX description
  • If tests KO: STOP and report the blocker

4. REPORT - Update the state

  • Mark the story as done in .claude/output/batch/progress.json
  • Log the time and modified files
  • Move on to the next story

Progress file

Automatic save in .claude/output/batch/progress.json:

{
  "started_at": "2026-03-23T10:00:00Z",
  "stories": {
    "US-001": { "status": "done", "commit": "abc1234", "files": ["..."] },
    "US-002": { "status": "in_progress" },
    "US-003": { "status": "pending" }
  }
}

Resume after interruption

If progress.json exists, resume at the last in_progress or pending story.

Guardrails

  • Maximum 10 stories per batch (beyond that, split)
  • STOP if 2 consecutive stories fail
  • Each story must pass the tests before continuing
  • Commit after each story (no giant commits)
  • Unattended runs need file writes allowed: the foundation's settings allow Edit/Write; a project that narrowed them needs auto mode or those rules back, since this skill pre-approves nothing

Read the full file on GitHub · 110 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.

  1. 25d ago Changed · -5 lines 75e61c2e63bb
  2. 26d ago Changed · -1 lines 2b4c9152eb17
  3. 1mo ago First seen · 116 lines · 47 tokens per session scan A 8716d88fe73b

Subscribe to this mod's changes

work-batch is a skill published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 733 once invoked, about $0.0002 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-03.