octo-staged-review

octo-staged-review is a command for Claude Code from CES-Ltd/Lumi. It costs 11 tokens per session (861 once invoked), scanned A, original, MIT.

A command for reviewing code in two stages: first checking whether it matches the requested specification, then checking its code quality. It sends the review work to multiple external AI providers.

In plain words
What is it for?
Use it to review a whole task or selected files against requirements and then inspect the implementation for quality.
Why use it?
It separates “does it meet the requirements?” from “is it well written?”, so one concern does not hide the other. The multi-provider review adds independent assessments.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; names the AskUserQuestion tool; mentions Codex.

Part of the octo plugin — 10 skills, 47 commands shipped together

Good fit Use it to review a whole task or selected files against requirements and then inspect the implementation for quality.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ces-ltd/lumi/octo-staged-review
View source ↗ CES-Ltd/Lumi
Install

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.

Clone the repo
git clone --depth 1 https://github.com/CES-Ltd/Lumi

Made for: Claude Code.

Or install octo, the plugin that ships this one along with the rest of its 10 skills, 47 commands.

Wrote 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.

agentmods badge for octo-staged-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-staged-review/github.svg)](https://agentmods.dev/commands/ces-ltd/lumi/octo-staged-review)
Your own site
<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-staged-review"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-staged-review/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.

agentmods 80×15 button for octo-staged-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-staged-review"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-staged-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 861 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.00861
Opus 5 $0.00005 $0.00430
Sonnet 5 $0.00002 $0.00172
Haiku 4.5 $0.00001 $0.00086

Measured 12d ago against content hash 0cc6f825b6a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

octo-staged-review 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.

resources/seed/octopus/commands/octo-staged-review.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Staged Review — Two-Stage Pipeline

🤖 INSTRUCTIONS FOR CLAUDE

MANDATORY COMPLIANCE — DO NOT SKIP

When the user explicitly invokes /octo:staged-review, you MUST execute the structured workflow below. You are PROHIBITED from doing the task directly, skipping the review phases, 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 dispatch work to external providers (Codex, Gemini, etc.) for this command. You are PROHIBITED from:

  • ❌ Executing the entire task using only Claude-native tools
  • ❌ Using a single Agent subagent instead of multi-provider dispatch
  • ❌ Skipping provider dispatch because "I can handle this alone"

Multi-LLM orchestration is the purpose of this command. Single-model execution defeats its purpose.


🐙 CLAUDE OCTOPUS ACTIVATED — Two-Stage Review Pipeline


When the user invokes this command (e.g., /octo:staged-review or /octo:staged-review src/auth/):

Step 1: Determine Review Scope

AskUserQuestion({
  questions: [
    {
      question: "What should be reviewed?",
      header: "Review Scope",
      multiSelect: false,
      options: [
        {label: "Staged changes", description: "git diff --cached — what you're about to commit"},
        {label: "Recent commit", description: "Changes in the last commit (HEAD~1..HEAD)"},
        {label: "Working tree", description: "All uncommitted changes"},
        {label: "Specific path", description: "A file or directory (provide path as argument)"}
      ]
    }
  ]
})

If invoked with arguments (e.g., /octo:staged-review src/auth/), use that path directly and skip the question.

Step 2: Execute Staged Review

Read and follow the full skill instructions from: ${HOME}/.claude-octopus/plugin/.claude/skills/skill-staged-review.md

The skill runs two stages:

  1. Stage 1 (Spec Compliance) — Validate against intent contract
  2. Gate check — Stage 1 must pass before Stage 2
  3. Stage 2 (Code Quality) — Stub detection + multi-LLM quality review (Codex for logic, Gemini for security, Claude for architecture — synthesized into unified findings)
  4. Combined report — Unified verdict

Read the full file on GitHub · 103 lines

Changes

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.

  1. 12d ago First seen · 103 lines · 11 tokens per session scan A 0cc6f825b6a5

Subscribe to this mod's changes

octo-staged-review 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 861 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.