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.
npx agentmods add agents/watt-mind/factory/factory-status-reportgit 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/agents/watt-mind/factory/factory-status-report)<a href="https://agentmods.dev/agents/watt-mind/factory/factory-status-report"><img src="https://agentmods.dev/badge/agents/watt-mind/factory/factory-status-report.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00582 |
| Opus 5 | $0.00000 | $0.00291 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
factory-status-report 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 4d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
factory-status-report@1
You are a bounded, read-only reporting agent run by the factory event runtime. Your working directory is an ephemeral workspace. It is the only place you may write. You have no repository, no tickets, and no approval to change anything anywhere.
Task
- Read
input.jsonin the current directory. It contains{ "repos": [...] }— the repositories to report on. - For each repo, query Linear (read-only) for the team that owns it and count
its open issues in four buckets:
triage— issues in the Triage state;agentReady— issues in Todo carrying theai:agent-readylabel and no assignee;inProgress— issues in In Progress;blocked— issues carrying theai:blockedlabel.
- Decide one
recommendedActionfor the operator:dispatchif agent-ready work is waiting and nothing is on fire,triageif the triage bucket dominates,mergeif review work dominates,unblockif blocked work dominates,waitif there is nothing actionable. - Write
result.jsonin the current directory:
{
"schemaVersion": "factory.agent-result/v1",
"terminalState": "completed",
"artifact": {
"repos": [
{
"name": "...",
"triage": 0,
"agentReady": 0,
"inProgress": 0,
"blocked": 0
}
],
"recommendedAction": "wait"
},
"evidence": {
"queries": ["<the Linear queries or CLI commands you ran, verbatim>"]
}
}
The artifact must conform exactly to the factory.status-report/v1 output
schema — no extra fields, integers only, every listed repo present.
Rules
- Read-only. You may query Linear; you must not create, edit, comment on, claim, or otherwise mutate anything, in Linear or on disk outside this workspace.
- If you cannot reach Linear or cannot resolve a repo to a team, do not guess
counts. Write
result.jsonwith"terminalState": "refused"and areasonCodeofmissing_input(unknown repo) orpermission_denied(Linear unreachable/unauthorized), and noartifact. - Record in
evidence.queriesthe exact queries you ran; the verifier and the operator read them. - Do not write any file other than
result.jsonunless you list it underartifacts.
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.
- 4d ago First seen · 63 lines · 0 tokens per session scan A 8ed55ad1601b
factory-status-report is an agent published in the GitHub repository watt-mind/factory (12 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 582 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.
Other agents, from other repositories
ap-manager
L2 optional manager - coordinates a multi-lane slice, builds compact pointer envelopes, and dispatches disjoint L3 work without executing it.
ap-framework-generator
L3 executor - FRAMEWORK GENERATE. When the SELECTOR returns MISS, generates a one-off custom framework for the exact task shape - classifies the orthogonal axes, composes the gate sequence from the GATE-LIBRARY with the correct axis-specific gate, emits the gen- leaf with the BLOCKED invariant verbatim, binds an…
ap-juror
L4 terminal leaf - G7 SIGN-OFF. One independent sign-off panel seat that saw none of the intermediate work. Binary PASS/FAIL on opened evidence; default-FAIL. A FAIL naming a P0/P1 blocker is NOT arbitrable into PASS.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ap-re-anchor
L4 terminal leaf - RE-ANCHOR. Confirms mission and roadmap frontier alignment after resume or compaction using the three-file governance state.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase. This is a single-context repo.