monitor-workers

A command for supervising worker agents working in separate worktrees, which are isolated working copies of a code repository. It checks for stalled work, gives available issues to idle workers, and deploys when everything is finished.

In plain words
What is it for?
Use it to monitor worker status, detect stale tasks, assign ready issues through cmux or tmux, and deploy completed work.
Why use it?
It reduces the manual effort of tracking parallel coding work and keeping unblocked workers busy.

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/laird/agents/monitor-workers
Clone the repo
git clone --depth 1 https://github.com/laird/agents
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 6,740 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin unknown 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.06740
Opus 5 $0.00000 $0.03370
Sonnet 5 $0.00000 $0.01348
Haiku 4.5 $0.00000 $0.00674

Measured yesterday against content hash e6f59f9cda1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

monitor-workers scanned grade B with 1 finding 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 yesterday.

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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

find "$HOME/.claude/plugins/cache" -type d -name "scripts" -path "*/autocoder/*" 2>/dev/null | sort -V | tail -1
plugins/autocoder/commands/monitor-workers.md · 586 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday First seen · 586 lines · 0 tokens per session scan B e6f59f9cda1f

Subscribe to this mod's changes

monitor-workers is a command published in the GitHub repository laird/agents (5 stars, last pushed yesterday), with no licence file. It costs nothing until one of its globs matches a file; then it loads 6,740 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.