A control-room command for a software factory, meaning a workflow that tracks automated development work through GitHub issues, pull requests, and run records. It reports queue state, review bottlenecks, blocked work, and items needing a person.

Use it to see factory status, identify the next human action, inspect the full queue, find blocked or stale items, or review everything connected to one issue.

It gives a quick, evidence-based view of what is waiting, stuck, under review, or requiring human action instead of relying on snapshot files alone.

factory — Command for Claude Code by addyosmani

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.

Clone the repo

git clone --depth 1 https://github.com/addyosmani/factory

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/addyosmani/factory/factory/github.svg)](https://agentmods.dev/commands/addyosmani/factory/factory)

Your own site

<a href="https://agentmods.dev/commands/addyosmani/factory/factory"><img src="https://agentmods.dev/badge/commands/addyosmani/factory/factory/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/addyosmani/factory/factory"><img src="https://agentmods.dev/badge/commands/addyosmani/factory/factory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 668 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.

Model	Per session	Once invoked
Fable 5.1	$0.00022	$0.00668
Opus 5.5	$0.00009	$0.00267
Sonnet 5.5	$0.00004	$0.00134
Haiku 4.5	$0.00002	$0.00067

Measured 2mo ago against content hash a92aef3eaba7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

factory 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 2mo 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/.claude/commands/factory.md · 73 lines

How it starts

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

You are the factory control room. The human wants to know what is going on and what needs them, quickly.

Read docs/factory/CONTRACT.md and docs/factory/CHARTER.md. Query open issues with factory:* labels and open factory PRs, then read the newest records under docs/factory/runs/. Treat QUEUE.md and STATE.md as snapshots only.

If the user passed an argument, handle it:

status (or no argument) - the report below
next - the single highest-value thing for a human to do right now, and why
queue - the full queue grouped by disposition
stuck - only items blocked, stale, or twice-rejected
<issue-number> - everything about that one item

The status report

Lead with what needs a human. Nothing else is urgent.

FACTORY - <repo> - tier: <tier>

NEEDS YOU (<n>)
  PR #<n>  <title>
           <why it needs you: load-bearing / tests modified / gate skipped / verifier reservations>
  FQ-<n>   needs-info: <the actual question>

REVIEW QUEUE: <n> / <charter limit>
  <if at or over the limit, say plainly: the factory should stop taking new work
   until this drains. The constraint is not how many agents can run, it is how
   many decisions are pending your judgment.>

RUNNING
  <issues labeled factory:in-progress and visible routine runs, with links>

QUEUE
  ready-to-implement  <n>
  ready-to-spec       <n>
  needs-info          <n>
  wait-to-implement   <n>
  awaiting-review     <n>

HEALTH
  gates on main: GREEN | RED (<failing>) | MISCONFIGURED (<missing>)
  skipped gates: <list, or none>
  charter gaps:  <n>  <- unreviewed decisions the factory could not make
  last monitor:  <date>  <- if over a week, say the loop is not closed

FLOW (last 30 days, when records are complete)
  verifier rejection rate: <n>%
  median review wait:      <duration>
  escaped defects:         <n>

SUGGESTED NEXT
  <one thing, with the reason>

Rules

Never merge, approve, or close anything from this command. It reports.
If the review queue is at the charter limit, lead with that above everything else. A full review queue is the binding constraint on the whole factory and everything else is noise until it drains.
If gates are red on the default branch, lead with that instead: every verdict since it broke was measured against a broken baseline.
Be terse. This is a dashboard. Long prose defeats the purpose.
If no run record has landed in over a week, say so. Stale evidence reads as calm.

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

2mo ago First seen · 73 lines · 22 tokens per session scan A a92aef3eaba7

Subscribe to this mod's changes

factory is a command published in the GitHub repository addyosmani/factory (324 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 668 once invoked, about $0.0001 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-08-30.

Claude Code Project management agentic-engineering codex software-factory

factory next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
factoryaddyosmani/factory	Command	324	2mo ago	MIT	A	22	Claude Code
implementshanraisshan/claude-code-best-practice	Command	69k	yesterday	MIT	A	6	Claude Code
ticketowainlewis/youtube-tutorials	Command	412	1mo ago	MIT	A	19	Claude Code
session-stopsageox/ox	Command	67	yesterday	MIT	A	0	Claude Code
scantrustmybot/plugin	Command	6	yesterday	MIT	A	51	Claude Code
speckit.archive.runracecraft-lab/Paddock	Command	12	4mo ago	MIT	A	16	Claude Code
skill-go-gin-apidewtech-technologies/dare-method	Command	5	3mo ago	MIT	A	0	Claude Code