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/watt-mind/factoryWrote 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/watt-mind/factory/factory-sweep)<a href="https://agentmods.dev/commands/watt-mind/factory/factory-sweep"><img src="https://agentmods.dev/badge/commands/watt-mind/factory/factory-sweep/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/watt-mind/factory/factory-sweep"><img src="https://agentmods.dev/badge/commands/watt-mind/factory/factory-sweep.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.00023 | $0.01255 |
| Opus 5.5 | $0.00009 | $0.00502 |
| Sonnet 5.5 | $0.00005 | $0.00251 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade A, and why
factory-sweep 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find tickets in this project's backlog that no longer need to exist, and retire them — never delete them. "Retire" means moving to Linear's Canceled or Duplicate state with a comment citing the evidence. Those states already exist for exactly this (docs/protocol.md §4) and keep the ticket recoverable; an actual delete does not, so never call a delete/archive mutation, only a state transition.
Resolve the team/project from the repo via config/repos.yaml (docs/protocol.md §1–2), or from $ARGUMENTS if a project name is given. Use factory ticket; on failure retry once then fall back to factory ticket raw per the floor.
First, before judging anything: git fetch --quiet and check git rev-list --count HEAD..origin/<base> (never @{upstream} — it depends on tracking config the checkout may not have). This stage's entire job is deciding what is already true of the code, so it is the stage a stale checkout hurts most — a feature merged last week reads as unshipped and its ticket keeps a dispatch slot it no longer deserves. Follow the floor's Checkout freshness rule: fast-forward a clean tree, and read origin/<base> rather than the working tree when it's dirty, ahead, or the fetch/rev-list itself fails. State the ref you swept against at the top of the report.
Scope
Target open tickets not currently live: Backlog, Triage, and Todo (including ai:agent-ready ones — the queue is exactly where an overtaken ticket keeps wasting a future dispatch slot if it isn't caught here). Interpret $ARGUMENTS as specific issue IDs or a max count; default up to 20, oldest-updated first — a ticket nobody has touched in months is the one most likely to have been overtaken by events, though age alone is never the verdict (see below).
Skip, always: anything In Progress, In Review, or carrying ai:blocked — those are live claims or holds owned by other stages, not this one's to touch.
Claim what you are examining
Same protocol as triage/unblock: before judging an issue, set assignee to yourself and add ai:in-progress + agent:<your-harness>; remove it when you finish that issue, whether you acted or left it alone. One at a time, not a batch up front.
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 · 50 lines · 23 tokens per session scan A f7dc737e45bc
factory-sweep is a command published in the GitHub repository watt-mind/factory (19 stars, last pushed 16d ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,255 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-31.
Other commands, from other repositories
roadmap-wave
Calcula a fronteira de elegibilidade do roadmap de um projeto-alvo e, mediante confirmacao explicita (interativa ou --yes), lanca a proxima leva paralela via parallel-launch.sh emit. Ponto de entrada avulso — reusa por referencia o fluxo de agente-00c.md §6.ter, sem duplicar.
feature-00c-abort
Aborta manualmente feature-00c para um short-name. SIGTERM + grace period 60s para persistir state; force-acquire do lock como fallback (FR-025). Marca abortada, gera relatorio parcial, commit local. Idempotente.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
triage
Process the user-feedback queue — triage new reports, keep the status mirror honest, and (at release time only) send the shipped emails.
aigon-feedback-triage
Run a triage loop for one feedback item with explicit human confirmation before writes.