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-scheduler)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-scheduler"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-scheduler/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-scheduler"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-scheduler.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.00546 |
| Opus 5 | $0.00006 | $0.00273 |
| Sonnet 5 | $0.00003 | $0.00109 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
octo-scheduler 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
Usage
${HOME}/.claude-octopus/plugin/scripts/scheduler/octopus-scheduler.sh start
${HOME}/.claude-octopus/plugin/scripts/scheduler/octopus-scheduler.sh stop
${HOME}/.claude-octopus/plugin/scripts/scheduler/octopus-scheduler.sh status
${HOME}/.claude-octopus/plugin/scripts/scheduler/octopus-scheduler.sh emergency-stop
Instructions for Claude
This command supports natural language. The user may invoke it with explicit subcommands OR with conversational requests. You MUST interpret intent and map to the correct action.
Step 1: Parse Intent
Map the user's input to one of these actions:
| Intent patterns | Action |
|---|---|
| "start", "run", "launch", "boot up", "turn on" | start |
| "stop", "shut down", "turn off", "kill", "halt" | stop |
| "status", "how is it", "what's running", "check", "is it running", no args | status |
| "emergency", "panic", "abort", "kill everything", "stop all" | emergency-stop |
If the intent is ambiguous, use AskUserQuestion to clarify.
Step 2: Display Banner
🐙 **CLAUDE OCTOPUS ACTIVATED** - Scheduler Management
⏰ Scheduler: [action description]
Providers:
🔵 Claude - Daemon management
Step 3: Execute and Present
Run the appropriate octopus-scheduler.sh subcommand and present results.
After status, give a human-readable summary:
- Whether the daemon is running and for how long
- How many jobs are active
- Current daily spend
- If any kill switches are active, explain what they mean and how to clear them
After start, confirm it's running and remind the user to add jobs if none exist.
After emergency-stop, explain what happened and how to recover:
- "Remove
~/.claude-octopus/scheduler/switches/KILL_ALLto allow restart"
Natural Language Examples
- "is the scheduler running?" →
status - "start the scheduler" →
start - "shut it down" →
stop - "something's wrong, stop everything" →
emergency-stop - "what's the scheduler doing?" →
status
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 · 67 lines · 13 tokens per session scan A c0faf8e0bfb8
octo-scheduler 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 546 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.