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/PrabhdeepSingh/claude-pluginsWrote 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/prabhdeepsingh/claude-plugins/factory)<a href="https://agentmods.dev/commands/prabhdeepsingh/claude-plugins/factory"><img src="https://agentmods.dev/badge/commands/prabhdeepsingh/claude-plugins/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.
<a href="https://agentmods.dev/commands/prabhdeepsingh/claude-plugins/factory"><img src="https://agentmods.dev/badge/commands/prabhdeepsingh/claude-plugins/factory.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.00108 | $0.14179 |
| Opus 5.5 | $0.00043 | $0.05672 |
| Sonnet 5.5 | $0.00022 | $0.02836 |
| Haiku 4.5 | $0.00011 | $0.01418 |
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 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/factory — the queue frontend
Contract: this command is the human-triggered replacement for a polling daemon. It resolves the tracker, shows what is authorized, claims one ticket, and hands it to the workflow that owns that stage. It contains no build phases of its own — implementation is /sonu:build, review is the skills build already runs, and merging is /sonu:ship. It never applies a trigger, and it merges only by delegation: the ship route (Phase 6) hands a human-authorized ticket to /sonu:ship, where the human's factory-ready-to-ship trigger is the merge authorization. Outside that route, it never merges.
Two front doors reach the same build engine. Describe work in chat and /sonu:build runs its own design gate. Route work through a ticket and this command claims it, then invokes that same /sonu:build — with the design gate already satisfied by the human-approved spec.
Apply this to $ARGUMENTS — the text typed after the command. If that token appears literally or is empty, run the default pass in Phase 3.
Shell discipline — every Bash call is a fresh shell. No variable survives between snippets. Each fence below declares what it uses; substitute literal values where a snippet says to. Never drop a leading declaration because "it was set earlier" — it was not, and an empty variable here fails silently: an empty ticket id turns a claim into a no-op that reads as success.
Phase 0 — Resolve the tracker
Load Skill(sonu:ticket-lifecycle) and resolve the configured tracker from .sonu/factory-config.md, falling back to ~/.sonu/factory-config.md. Read only the resolved tracker's adapter.
CONFIG=""
if [ -f .sonu/factory-config.md ]; then CONFIG=".sonu/factory-config.md"
elif [ -f "$HOME/.sonu/factory-config.md" ]; then CONFIG="$HOME/.sonu/factory-config.md"
fi
# Three outcomes, never two — a config that exists but cannot be read must NOT
# report "no config" (that message sends the user to re-init a file they have).
if [ -z "$CONFIG" ]; then
echo "STOP: no factory config — run /sonu:factory init"
elif [ -s "$CONFIG" ] && sed -n '2,/^---$/p' "$CONFIG"; then
echo "config: $CONFIG"
else
echo "STOP: config exists at $CONFIG but is empty or could not be read — fix it before running a pass"
fi
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 · 392 lines · 108 tokens per session scan A a73dbbf605a0
factory is a command published in the GitHub repository PrabhdeepSingh/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 108 tokens to every session and 14,179 once invoked, about $0.0004 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
ralph-build
Implement the next task from the queue.
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
scout-work
Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.
sync
Reconcile coco tracker state with the configured issue tracker. Syncs task statuses and reports mismatches.