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-deliver)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-deliver"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-deliver/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-deliver"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-deliver.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.00017 | $0.00973 |
| Opus 5 | $0.00009 | $0.00487 |
| Sonnet 5 | $0.00003 | $0.00195 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
octo-deliver 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.
This is a copy
88% identical to octo-deliver — 13 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deliver - Delivery Phase ✅
🤖 INSTRUCTIONS FOR CLAUDE
MANDATORY COMPLIANCE — DO NOT SKIP
When the user explicitly invokes /octo:deliver, you MUST execute the structured workflow below. You are PROHIBITED from doing the task directly, skipping the validation/review 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:deliver <arguments>):
✓ CORRECT - Use the Skill tool:
Skill(skill: "octo:deliver", args: "<user's arguments>")
✗ INCORRECT:
Skill(skill: "flow-deliver", ...) ❌ Wrong! Internal skill name, not resolvable by Skill tool
Task(subagent_type: "octo:deliver", ...) ❌ Wrong! This is a skill, not an agent type
Auto Code Review & E2E Verification (MANDATORY)
Before presenting results, launch two verification agents in parallel:
Agent(model: "sonnet", subagent_type: "feature-dev:code-reviewer", run_in_background: true,
description: "Code review: deliver phase",
prompt: "Review code changes from this session. Check git diff. Report only high-confidence bugs, security issues, and convention violations.")
Agent(model: "sonnet", run_in_background: true,
description: "E2E test: deliver phase",
prompt: "Run the project's test suite. Report tests passed/failed and any regressions.")
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 · 122 lines · 17 tokens per session scan A e42fba441fbf
octo-deliver is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 973 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to octo-deliver, differing in 13 lines, and is treated as a copy.
Other commands, from other repositories
full-review
Orchestrate comprehensive multi-dimensional code review using specialized review agents across architecture, security, performance, testing, and best practices.
codex-loop
Use Codex as a second, differently-trained reviewer of your branch, fix every real finding with regression tests, and loop until two consecutive reviews come back clean. Runs autonomously.
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.
team-review
Launch a multi-reviewer parallel code review with specialized review dimensions.
eval
Manage eval-driven development workflow (define, check, report, list).
speckit.verify
Validates implementation completion by checking tasks, logic, tests, and code quality against specifications. Use when you need to verify that all tasks are properly completed.