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-resume)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-resume"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-resume/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-resume"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-resume.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.00015 | $0.00511 |
| Opus 5 | $0.00008 | $0.00255 |
| Sonnet 5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
octo-resume 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.
What it actually says
/octo:resume — Agent Resume
MANDATORY COMPLIANCE — DO NOT SKIP
When the user invokes /octo:resume, you MUST follow the resume workflow below. You are PROHIBITED from:
- Starting fresh instead of resuming the previous agent's work
- Skipping the agent ID lookup and just doing the task from scratch
- Deciding it's "easier to start over" than to resume
The user chose /octo:resume because they want to continue interrupted work, not restart it.
Your first output line MUST be: 🐙 Octopus Agent Resume
Resume a previously-running Claude agent by ID. Picks up the agent's transcript and continues where it left off.
Step 1: Get the Agent ID
If you don't have the agent ID:
- Check
/octo:sentineloutput for running agent IDs - Look in
~/.claude-octopus/results/for recent result files (filename prefix contains agent type + task ID) - The agent ID was shown when the agent was originally spawned
Step 2: Resume
Use the Bash tool to execute:
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh agent-resume "$ARGUMENTS"
Pass the agent ID as $ARGUMENTS. Optionally append a follow-up prompt:
# Just agent ID (resumes with "Continue where you left off.")
orchestrate.sh agent-resume abc123
# Agent ID + custom prompt
orchestrate.sh agent-resume abc123 "fix the failing test in auth.ts"
Requirements
- Claude Code v2.1.34+ (
SUPPORTS_CONTINUATION=true,SUPPORTS_STABLE_AGENT_TEAMS=true) - Agent Teams enabled (required for agent transcript access)
- Agent must have been a Claude agent (not Codex/Gemini — those don't support transcripts)
- CC v2.1.77+: Resume uses
SendMessage(auto-resumes stopped agents). TheAgent(resume:)parameter was removed in v2.1.77.
Run /octo:doctor to verify flags are active.
Fallback
If continuation is not supported, spawn a fresh agent with /octo:develop and describe what was in progress.
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 · 58 lines · 15 tokens per session scan A d3ebc7c3a42e
octo-resume is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 511 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.