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.
npx agentmods add commands/ces-ltd/lumi/octo-debuggit 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-debug)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-debug"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-debug.svg" alt="Measured on agentmods" 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.00008 | $0.00263 |
| Opus 5 | $0.00004 | $0.00131 |
| Sonnet 5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
octo-debug 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 5d 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
86% identical to octo-debug — 3 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.
What it actually says
Debug - Systematic Debugging Skill
Your first output line MUST be: 🐙 Octopus Debug Mode
Instructions
Read and follow the full skill instructions from:
${HOME}/.claude-octopus/plugin/.claude/skills/skill-debug.md
Quick Usage
Just use natural language:
"Debug why the login is failing"
"Help me debug this memory leak"
"Systematically debug the API timeout issue"
Debugging Approach
- Reproduce: Understand and reproduce the issue
- Isolate: Narrow down the root cause
- Analyze: Examine code, logs, and state
- Hypothesize: Form theories about the bug
- Test: Validate hypotheses
- Fix: Implement and verify the solution
What You Get
- Step-by-step debugging plan
- Root cause analysis
- Fix recommendations
- Prevention strategies
- Test cases to prevent regression
Natural Language Examples
"Debug the failing test in test_auth.py"
"Help me debug why the API is returning 500 errors"
"Systematic debugging of the memory usage issue"
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.
- 5d ago First seen · 47 lines · 8 tokens per session scan A 062e59919872
octo-debug is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 263 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to octo-debug, differing in 3 lines, and is treated as a copy.
Other commands, from other repositories
setup
Full onboarding for a new project — runs /doctor diagnostics, then injects the CLAUDE.md template + nav-ref instrumentation + Zustand store exposure so the plugin works without the user having to read documentation.
run-action
Execute a learned Maestro flow ("action") by name with optional -e KEY=VALUE parameters. Looks the flow up via packages/rn-dev-agent-core/dist/learned-actions.js (same inventory as /rn-dev-agent:list-learned-actions), then replays it via cdprunaction — auto-repair-aware orchestration with structured RunRecords (GH.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
nav-graph
Extract, inspect, and query the app navigation graph — a complete map of all screens and navigators.
doctor
Diagnose installation health. Check Node, CDP bridge, rn-fast-runner (iOS), rn-android-runner (Android), maestro-runner, simulators, Metro, CDP, injected helpers, ffmpeg, physical devices, plugin version, Vercel rules sync. Reports what's missing — does NOT modify your project.
check-env
Check that the fenced React Native session, Metro, app target, and device inventory are ready for testing.