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-km)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-km"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-km/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-km"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-km.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.00012 | $0.00465 |
| Opus 5 | $0.00006 | $0.00233 |
| Sonnet 5 | $0.00002 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
octo-km 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.
What it actually says
Knowledge Mode Toggle
Toggle between Dev Work Mode and Knowledge Work Mode.
Implementation Instructions
When this command is executed:
-
Parse the argument:
- No argument or "on": Switch to Knowledge Work mode (set
knowledge_mode: true) - "off": Switch to Dev Work mode (set
knowledge_mode: false)
- No argument or "on": Switch to Knowledge Work mode (set
-
Check for config file:
- Config file:
.claude/claude-octopus.local.md - If file doesn't exist when switching, create it
- Use bash
test -fto check existence before reading
- Config file:
-
Switch to Knowledge Work mode (no argument or "on"):
- Create/update
.claude/claude-octopus.local.mdwith YAML frontmatter - Set
knowledge_mode: true - Confirm with emoji 🎓 and active personas
- Create/update
-
Switch to Dev Work mode ("off"):
- Create/update
.claude/claude-octopus.local.mdwith YAML frontmatter - Set
knowledge_mode: false - Confirm with emoji 🔧 and active personas
- Create/update
Usage
/octo:km # Switch to Knowledge Work mode (default action)
/octo:km on # Switch to Knowledge Work mode (explicit)
/octo:km off # Switch to Dev Work mode (same as /octo:dev)
Two Work Modes
Dev Work Mode 🔧 (default)
- Best for: Building features, debugging code, implementing APIs
- Personas: backend-architect, code-reviewer, debugger, test-automator
Knowledge Work Mode 🎓
- Best for: User research, strategy analysis, literature reviews
- Personas: ux-researcher, strategy-analyst, research-synthesizer
Both modes use the same AI providers (Codex + Gemini), just optimized with different personas.
Quick Switch
/octo:dev- Switch to Dev Work mode 🔧/octo:km- Switch to Knowledge Work mode 🎓
Your mode choice persists across sessions.
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.
- 12d ago First seen · 58 lines · 12 tokens per session scan A 8214a356bf3a
octo-km is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 465 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
evolve
Cluster related instincts into skills, commands, or agents.
suggest-automation
A command that reviews recent Git commits and project instructions to find work patterns that happen repeatedly.
instinct-import
Import instincts from teammates, Skill Creator, or other sources.
instinct-export
Export instincts for sharing with teammates or other projects.
context-stats
Display context window usage and token statistics.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.