auto-work-all

auto-work-all is a command for coding agents from shwilliamson/automatasaurus. It costs 0 tokens per session (1,776 once invoked), scanned A, original, MIT.

A command for processing all open GitHub issues, which are tracked tasks or bugs, through separate coding-agent workflows. It selects work, coordinates implementation and reviews, and can merge successful pull requests.

In plain words
What is it for?
Use it to implement a backlog of open issues automatically, follow an implementation plan, coordinate reviews, and merge completed changes.
Why use it?
It removes the need to start and track each issue manually. It uses dependencies, priorities, existing plans, and configured limits to control the work.

Command

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.

agentmods
npx agentmods add commands/shwilliamson/automatasaurus/auto-work-all
Clone the repo
git clone --depth 1 https://github.com/shwilliamson/automatasaurus

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 auto-work-all

README.md
[![agentmods](https://agentmods.dev/badge/commands/shwilliamson/automatasaurus/auto-work-all.svg)](https://agentmods.dev/commands/shwilliamson/automatasaurus/auto-work-all)
Your own site
<a href="https://agentmods.dev/commands/shwilliamson/automatasaurus/auto-work-all"><img src="https://agentmods.dev/badge/commands/shwilliamson/automatasaurus/auto-work-all.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,776 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01776
Opus 5 $0.00000 $0.00888
Sonnet 5 $0.00000 $0.00355
Haiku 4.5 $0.00000 $0.00178

Measured 5d ago against content hash 74ee2f3a4e5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

auto-work-all 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 5d 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.

template/commands/auto-work-all.md · 276 lines

How it starts

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

Work All - Process All Open Issues

Autonomously work through all open GitHub issues using context-isolated subagents.

Workflow Mode

WORKFLOW_MODE: all-issues
AUTO_MERGE: true (handled by this orchestrator (aka Product Owner) after /auto-work-issue completes)

Instructions

You are the Autonomous Implementation Orchestrator. You:

  1. Select issues based on dependencies and priority
  2. Spawn /auto-work-issue {n} as a subagent for each issue (context isolation)
  3. Parse subagent output to determine result
  4. Merge successful PRs
  5. Enforce circuit breaker limits

Load Context

  1. Load the workflow-orchestration skill
  2. Load the github-workflow skill 2b. If agent teams are enabled (CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in settings), also load the team-coordination skill
  3. Check for implementation plan files (implementation-plan*.md). If multiple exist, use the highest-numbered one (e.g., implementation-plan-3.md over implementation-plan.md)
  4. Read circuit breaker limits from .claude/settings.json under automatasaurus.limits

Circuit Breaker Limits

Before each iteration, check limits from settings:

Limit Default Action When Exceeded
maxIssuesPerRun 20 Stop, report progress
maxEscalationsBeforeStop 3 Stop, notify human
maxConsecutiveFailures 3 Stop, notify human

Initialize counters:

issuesProcessed = 0
escalationCount = 0
consecutiveFailures = 0

Main Loop

LOOP:
  1. CHECK LIMITS
     - If issuesProcessed >= maxIssuesPerRun → Stop (limit reached)
     - If escalationCount >= maxEscalationsBeforeStop → Stop (escalation limit)
     - If consecutiveFailures >= maxConsecutiveFailures → Stop (failure limit)

  2. LIST OPEN ISSUES
     - Check milestones and priorities
     - If no open issues → Notify complete, exit

  3. SELECT NEXT ISSUE
     - Follow latest implementation-plan file if exists
     - Otherwise use selection criteria (see below)
     - Check dependencies (skip if blocked)

  4. SPAWN /auto-work-issue SUBAGENT
     - Use Task tool to spawn: "Run /auto-work-issue {issue_number}"
     - Wait for completion
     - Parse output for result

  5. PARSE RESULT
     - SUCCESS: Output contains "PR #X is ready" or "All required reviews complete"
     - BLOCKED: Output contains "blocked" or "dependency"
     - ESCALATED: Output contains "Escalating" or "stuck"

  6. HANDLE RESULT
     - SUCCESS: Merge PR, reset consecutiveFailures, increment issuesProcessed
     - BLOCKED: Skip issue, continue to next
     - ESCALATED: Increment escalationCount, consecutiveFailures

  7. CONTINUE
     - Report progress
     - Loop back to step 1

END LOOP

Read the full file on GitHub · 276 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. 5d ago First seen · 276 lines · 0 tokens per session scan A 74ee2f3a4e5b

Subscribe to this mod's changes

auto-work-all is a command published in the GitHub repository shwilliamson/automatasaurus (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,776 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-08-31.