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 skills add CES-Ltd/Lumi --skill octopus-architecturegit 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/skills/ces-ltd/lumi/octopus-architecture)<a href="https://agentmods.dev/skills/ces-ltd/lumi/octopus-architecture"><img src="https://agentmods.dev/badge/skills/ces-ltd/lumi/octopus-architecture/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/skills/ces-ltd/lumi/octopus-architecture"><img src="https://agentmods.dev/badge/skills/ces-ltd/lumi/octopus-architecture.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.01265 |
| Opus 5 | $0.00008 | $0.00633 |
| Sonnet 5 | $0.00003 | $0.00253 |
| Haiku 4.5 | $0.00002 | $0.00127 |
Grade A, and why
octopus-architecture 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ EXECUTION CONTRACT (MANDATORY - CANNOT SKIP)
This skill uses ENFORCED execution mode. You MUST follow this exact sequence.
STEP 1: Display Visual Indicators (MANDATORY - BLOCKING)
MANDATORY: Run the centralized provider check BEFORE displaying the banner:
bash "${HOME}/.claude-octopus/plugin/scripts/helpers/check-providers.sh"
Use the ACTUAL results. PROHIBITED: Showing only "🔵 Claude: Available ✓" without listing all providers.
Display this banner BEFORE orchestrate.sh execution (list ALL providers from check output):
🐙 **CLAUDE OCTOPUS ACTIVATED** - Architecture design mode
🏗️ Architecture: [Brief description of system to design]
Provider Availability:
🔴 Codex CLI: [status from check] - Backend architecture patterns
🟡 Gemini CLI: [status from check] - Alternative approaches
🟢 Copilot CLI: [status from check] - GitHub integration
🟣 Qwen CLI: [status from check] - Additional perspective
🟤 OpenCode CLI: [status from check] - Multi-provider routing
🔵 Claude: Available ✓ - Synthesis and recommendations
💰 Estimated Cost: $0.02-0.08
⏱️ Estimated Time: 3-7 minutes
Validation:
- If ALL external CLI providers unavailable → STOP, suggest:
/octo:setup - If some unavailable → Continue with available provider(s)
- If multiple available → Proceed normally
DO NOT PROCEED TO STEP 2 until banner displayed.
STEP 2: Execute orchestrate.sh spawn (MANDATORY - Use Bash Tool)
You MUST execute this command via the Bash tool:
${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh spawn backend-architect "<user's architecture request>"
CRITICAL: You are PROHIBITED from:
- ❌ Designing architecture directly without calling orchestrate.sh
- ❌ Using direct analysis as a substitute
- ❌ Claiming you're "simulating" the workflow
- ❌ Proceeding to Step 3 without running this command
This is NOT optional. You MUST use the Bash tool to invoke orchestrate.sh.
STEP 3: Verify Execution (MANDATORY - Validation Gate)
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 · 181 lines · 15 tokens per session scan A b96de52123b7
octopus-architecture is a skill published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 1,265 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 skills, from other repositories
api-interface-design
Use when designing public APIs, module boundaries, provider adapters, tool schemas, or data contracts.
architecture-patterns
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
sglang
Fast structured generation and serving for LLMs with RadixAttention prefix caching. Use for JSON/regex outputs, constrained decoding, agentic workflows with tool calls, or when you need 5× faster inference than vLLM with prefix sharing. Powers 300,000+ GPUs at xAI, AMD, NVIDIA, and LinkedIn.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
error-handling-patterns
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.