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-design-ui-ux)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-design-ui-ux"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-design-ui-ux/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-design-ui-ux"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-design-ui-ux.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.00018 | $0.00896 |
| Opus 5 | $0.00009 | $0.00448 |
| Sonnet 5 | $0.00004 | $0.00179 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
octo-design-ui-ux 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.
This is a copy
91% identical to octo-design-ui-ux — 5 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/octo:design-ui-ux - UI/UX Design Workflow
INSTRUCTIONS FOR CLAUDE
When the user invokes this command (e.g., /octo:design-ui-ux <arguments>):
Step 1: Detect Mode
Parse the user's intent to determine which mode to run:
| Intent | Mode | What Happens |
|---|---|---|
| "design a dashboard" | Full design system | 4-phase workflow via skill |
| "pick colors for X" | Quick search | Single BM25 query, immediate results |
| "review this Figma" | Design review | Pull Figma context, create specs |
| "create component specs" | Component spec | Focused spec generation |
For full design system requests, invoke the skill skill-ui-ux-design.md which runs the 4-phase Double Diamond workflow.
For quick searches, run the search directly:
python3 "${HOME}/.claude-octopus/plugin/vendors/ui-ux-pro-max-skill/src/ui-ux-pro-max/scripts/search.py" "<query>" --domain <domain>
Step 2: Check Design Intelligence Availability
if [ -f "${HOME}/.claude-octopus/plugin/vendors/ui-ux-pro-max-skill/src/ui-ux-pro-max/scripts/search.py" ]; then
python3 -c "import csv, re, math" 2>/dev/null && echo "Design intelligence: ready" || echo "Design intelligence: python3 required"
else
echo "Design intelligence: not installed (run: git submodule update --init)"
fi
If unavailable, fall back to Claude's built-in design knowledge with a note to the user.
Step 3: Display Banner
🐙 **CLAUDE OCTOPUS ACTIVATED** - UI/UX Design Mode
🎨 Design: [Brief description of what's being designed]
Tools:
🔍 BM25 Design Intelligence - Style, palette, typography, UX databases
🔵 Claude (ui-ux-designer) - Design synthesis and specification
🎨 Figma MCP - [Available ✓ / Not configured]
🧩 shadcn MCP - [Available ✓ / Not configured]
Step 4: Execute
Quick mode: Run search, present results, offer to expand into full design system.
Full mode: Execute the design workflow:
- Discover - Search BM25 databases, detect project context, pull Figma if available
- Define - Synthesize search results into design direction (style, palette, typography, layout)
- Critique - Adversarial review of the design direction via Codex/Gemini (or Claude self-critique). Catches accessibility failures, impractical choices, and research blind spots before they become tokens
- Develop - Generate design tokens, component specs, page layouts (incorporating critique fixes)
- Deliver - Validate accessibility, create handoff specs, push to Figma if connected
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 · 101 lines · 18 tokens per session scan A 41c725dec6cd
octo-design-ui-ux is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 896 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to octo-design-ui-ux, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.
designer
UI/UX design with Memory coordination for consistent experiences.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.