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-discover)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-discover"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-discover/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-discover"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-discover.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.00011 | $0.01306 |
| Opus 5 | $0.00005 | $0.00653 |
| Sonnet 5 | $0.00002 | $0.00261 |
| Haiku 4.5 | $0.00001 | $0.00131 |
Grade A, and why
octo-discover 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 11d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discover - Discovery Phase 🔍
🤖 INSTRUCTIONS FOR CLAUDE
MANDATORY COMPLIANCE — DO NOT SKIP
When the user explicitly invokes /octo:discover, you MUST execute the structured workflow below. You are PROHIBITED from doing the task directly, skipping the multi-provider research phase, or deciding the task is "too simple" for this workflow. The user chose this command deliberately — respect that choice.
EXECUTION MECHANISM — NON-NEGOTIABLE
You MUST execute this command by invoking the corresponding skill via the Skill tool. You are PROHIBITED from:
- ❌ Using the Agent tool to research/implement yourself instead of invoking the skill
- ❌ Using WebFetch/Read/Grep as a substitute for multi-provider dispatch
- ❌ Skipping
orchestrate.shcalls because "I can do this faster directly" - ❌ Implementing the task using only Claude-native tools (Agent, Write, Edit)
Multi-LLM orchestration is the purpose of this command. If you execute using only Claude, you've violated the command's contract.
When the user invokes this command (e.g., /octo:discover <arguments>):
✓ CORRECT - Use the Skill tool:
Skill(skill: "octo:discover", args: "<user's arguments>")
✗ INCORRECT:
Skill(skill: "flow-discover", ...) ❌ Wrong! Internal skill name, not resolvable by Skill tool
Task(subagent_type: "octo:discover", ...) ❌ Wrong! This is a skill, not an agent type
Step 1: Ask Clarifying Questions
CRITICAL: Before starting discovery, use the AskUserQuestion tool to gather context:
Ask 3 clarifying questions to ensure focused research:
AskUserQuestion({
questions: [
{
question: "How thorough should the research be?",
header: "Research Intensity",
multiSelect: false,
options: [
{label: "Quick (1-2 min)", description: "2 agents — fast problem space scan"},
{label: "Standard (2-4 min)", description: "4-5 agents — balanced multi-perspective coverage (recommended)"},
{label: "Deep (3-6 min)", description: "6-7 agents — exhaustive analysis with web search"}
]
},
{
question: "What's your primary focus area?",
header: "Focus",
multiSelect: false,
options: [
{label: "Technical implementation (Recommended)", description: "Code patterns, APIs, architecture"},
{label: "Best practices", description: "Industry standards and conventions"},
{label: "Ecosystem & tools", description: "Libraries, frameworks, community"},
{label: "Trade-offs & comparisons", description: "Pros/cons analysis"}
]
},
{
question: "How should the output be formatted?",
header: "Output",
multiSelect: false,
options: [
{label: "Detailed report (Recommended)", description: "Comprehensive write-up"},
{label: "Summary", description: "Concise key findings"},
{label: "Comparison table", description: "Side-by-side format"},
{label: "Recommendations", description: "Actionable next steps"}
]
}
]
})
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.
- 11d ago First seen · 175 lines · 11 tokens per session scan A 881da4e08837
octo-discover is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 1,306 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.