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-prd)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-prd"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-prd/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-prd"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-prd.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.00019 | $0.01476 |
| Opus 5 | $0.00010 | $0.00738 |
| Sonnet 5 | $0.00004 | $0.00295 |
| Haiku 4.5 | $0.00002 | $0.00148 |
Grade A, and why
octo-prd 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 10d 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.
This is a copy
94% identical to octo-prd — 55 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY COMPLIANCE — DO NOT SKIP
When the user invokes /octo:prd, you MUST execute the multi-AI PRD generation workflow below. You are PROHIBITED from:
- Writing the PRD directly without multi-provider orchestration
- Skipping the scoring framework or quality gates
- Deciding the feature is "straightforward enough" to document without multi-LLM perspectives
- Producing a single-model PRD instead of a synthesized multi-perspective document
The user chose /octo:prd over writing a PRD manually. They want Codex + Gemini + Claude perspectives synthesized through the 100-point scoring framework.
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.
STOP - DO NOT INVOKE /skill OR Skill() AGAIN
This command is already executing. The feature to document is: $ARGUMENTS.feature
PHASE 0: CLARIFICATION (MANDATORY - DO THIS FIRST)
Before writing ANY PRD content, ask the user:
I'll create a PRD for: **$ARGUMENTS.feature**
To make this PRD highly targeted, please answer briefly:
1. **Target Users**: Who will use this? (developers, end-users, admins, agencies?)
2. **Core Problem**: What pain point does this solve? Any metrics on current impact?
3. **Success Criteria**: How will you measure success? (KPIs, adoption rate, time saved?)
4. **Constraints**: Any technical, budget, timeline, or platform constraints?
5. **Existing Context**: Greenfield project or integrating with existing systems?
(Type "skip" to proceed with assumptions, or answer inline)
WAIT for user response before proceeding.
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.
- 10d ago First seen · 172 lines · 19 tokens per session scan A c624a07c1720
octo-prd is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 1,476 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to octo-prd, differing in 55 lines, and is treated as a copy.
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.