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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/work-batch)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/work-batch"><img src="https://agentmods.dev/badge/commands/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.
<a href="https://agentmods.dev/commands/christopherlouet/claude-base/work-batch"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/work-batch.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.00000 | $0.00258 |
| Opus 5.5 | $0.00000 | $0.00103 |
| Sonnet 5.5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
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 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.
What it actually says
WORK-BATCH Agent
Autonomous and sequential execution of user stories from a PRD file (JSON or Markdown).
Context
$ARGUMENTS
Objective
Process a backlog of stories in autonomous mode: for each story, TDD cycle + atomic commit.
Workflow
For each story (priority order P1 → P2 → P3):
- LOAD: Read the story and its acceptance criteria
- TDD: Red-Green-Refactor
- COMMIT:
feat(scope): US-XXX description - REPORT: Save to
.claude/output/batch/progress.json
PRD Format
The PRD file can be in JSON (prd.json) or Markdown (prd.md). See the work-batch skill for detailed formats.
Guardrails
- Max 10 stories per batch
- STOP if 2 consecutive stories fail
- Atomic commit after each story
- Automatic resume if
progress.jsonexists
Expected output
- Each story implemented and committed
- Progress file updated
- Final summary with completed/failed stories
IMPORTANT: One commit = one story. No giant multi-story commits.
NEVER continue if tests fail on a story.
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 · 43 lines · 0 tokens per session scan A 14c26082a7a1
work-batch is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 258 tokens. 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.
Other commands, from other repositories
implement
Execute tasks from a track's implementation plan following TDD workflow.
test-plan
Generate a test strategy document — test matrix, coverage goals, and test pyramid allocation for the current project.
test-suite
Run comprehensive test suite with coverage analysis.
loop
Autonomous execution loop. Runs the TDD cycle repeatedly until all tasks in an epic are complete, with circuit breaker protection and PR workflow.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
tdd
Run the test-driven development workflow: write failing tests first, then the minimal code to pass.