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/CES-Ltd/LumiWrote 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/ces-ltd/lumi/octo-factory)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-factory"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-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/ces-ltd/lumi/octo-factory"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-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.00013 | $0.01348 |
| Opus 5 | $0.00006 | $0.00674 |
| Sonnet 5 | $0.00003 | $0.00270 |
| Haiku 4.5 | $0.00001 | $0.00135 |
Grade A, and why
octo-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 12d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Factory - Dark Factory Mode (v8.25.0)
MANDATORY COMPLIANCE — DO NOT SKIP
When the user invokes /octo:factory, you MUST execute the full autonomous pipeline below. You are PROHIBITED from:
- Building the software directly without running the spec-driven pipeline
- Skipping the embrace workflow or quality gates
- Deciding the spec is "simple enough" to implement without multi-provider synthesis
- Substituting a single-model implementation for the multi-LLM factory pipeline
The user chose Dark Factory deliberately. They want spec-in, software-out with full multi-AI orchestration, adversarial review, and quality gates. If you catch yourself thinking "I can just implement this directly" — STOP. That is the exact rationalization this instruction prohibits.
EXECUTION MECHANISM — NON-NEGOTIABLE
You MUST execute this command by calling orchestrate.sh as documented below. You are PROHIBITED from:
- ❌ Doing the work yourself using only Claude-native tools (Agent, Read, Grep, Write)
- ❌ Using a single Claude subagent instead of multi-provider dispatch via orchestrate.sh
- ❌ Skipping orchestrate.sh because "I can do this faster directly"
Multi-LLM orchestration is the purpose of this command. If you execute using only Claude, you've violated the command's contract.
INSTRUCTIONS FOR CLAUDE
When the user invokes this command (e.g., /octo:factory --spec <path>):
Step 1: Ask Clarifying Questions
CRITICAL: Before starting the factory pipeline, use the AskUserQuestion tool to gather context:
Ask 3 clarifying questions:
- Spec path — Where is the NLSpec file? (provide path, or paste inline)
- Satisfaction target — Accept spec default, or override? (Use spec default / Custom target 0.80-0.99)
- Cost confirmation — Factory mode runs
20-30 agent calls ($0.50-2.00). Proceed? (Yes / Yes with --ci for non-interactive / No)
After receiving answers: validate spec path exists, set overrides, proceed.
Step 2: Check Provider Availability & Display Banner
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.
- 12d ago First seen · 134 lines · 13 tokens per session scan A 32b3402bfaed
octo-factory is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 1,348 once invoked, about $0.0001 per session on Opus 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.
Other commands, from other repositories
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
workflow-classify
Classify task size (S/M/L/XL) and recommend the appropriate workflow pipeline.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
sonarqube
Analyze SonarCloud quality issues for a specific PR.
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.