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 OneXeor-Dev/lumo --skill skillgit clone --depth 1 https://github.com/OneXeor-Dev/lumoWrote 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/onexeor-dev/lumo/skill)<a href="https://agentmods.dev/skills/onexeor-dev/lumo/skill"><img src="https://agentmods.dev/badge/skills/onexeor-dev/lumo/skill/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/onexeor-dev/lumo/skill"><img src="https://agentmods.dev/badge/skills/onexeor-dev/lumo/skill.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.00104 | $0.11976 |
| Opus 5.5 | $0.00042 | $0.04790 |
| Sonnet 5.5 | $0.00021 | $0.02395 |
| Haiku 4.5 | $0.00010 | $0.01198 |
Grade A, and why
lumo 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 1mo 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 — 1,017 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lumo
Mobile design intelligence for Claude Code. Lumo combines a curated rule set with a small toolkit of deterministic Python tools — so checks that need real math (WCAG luminance, OKLCH correction, AST diff, cross-platform parity) return facts, not LLM guesses.
When to Use
Use Lumo when the user request touches any of:
- Accessibility / WCAG contrast questions on a colour pair or palette
- Reviewing or auditing mobile UI code (Jetpack Compose, Android XML, SwiftUI, UIKit)
- Comparing the same screen across iOS and Android for visual / behavioural parity (padding, animation timing, touch target, typography scale)
- Applying cognitive-science rules to a layout: Fitts (target size × distance), Hick (choice count → decision time), Gestalt grouping, Nielsen heuristics
- Choosing or validating colour tokens for a mobile design system
- Detecting platform-specific anti-patterns (e.g. emoji as system icons, hardcoded hex in components, missing safe-area handling)
When NOT to Use
Skip Lumo entirely for:
- Pure backend / API / database tasks
- Non-mobile web design (use a web-focused skill instead)
- Build / CI / dependency / version-bump tasks
- Performance work that doesn't touch UI rendering
- Tasks where the user has explicitly opted out of design feedback
Do not invoke Lumo "just in case" the request might be design-adjacent. If the request doesn't match a trigger above and the user hasn't named a mobile UI concern, stay out.
Tools
Lumo ships with Python tools. Each tool has a single CLI entry-point with
deterministic output. Invoke via Bash. Tools live in tools/lumo/<area>/cli.py
and are exposed as console scripts after pip install -e tools/ or
pipx install lumo-mobile.
When running inside an MCP-aware client (Cursor, Continue, Aider, Goose,
Zed, Codex, or Claude Code with MCP enabled), the same tools are
also exposed as MCP functions: lumo_wcag_check, lumo_wcag_fix,
lumo_theory_check, lumo_parity_diff, lumo_source_check_compose,
lumo_source_check_swiftui, lumo_audit_scan, lumo_figma_diff,
lumo_figma_render, lumo_render_compose, lumo_render_swiftui.
Prefer the MCP function over spawning a Bash subprocess when available
— the structured response is already JSON and the user does not see
noisy command output.
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.
- 1mo ago First seen · 1,017 lines · 104 tokens per session scan A 604b0a705c33
lumo is a skill published in the GitHub repository OneXeor-Dev/lumo (2 stars, last pushed 4mo ago), licensed MIT. It adds 104 tokens to every session and 11,976 once invoked, about $0.0004 per session on Opus 5.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-31.
Other skills, from other repositories
compose-ui
Writes and reviews composables for Compose and CMP: the Route/Screen/leaf split, state-read placement and stability, loading/empty/error UX states, LazyColumn lists and grids, animation choice, accessibility and semantics, design-system tokens, CMP Res resources, Coil images, and keyboard/focus. Use when touching…
android-design-system-pro
Bootstraps or audits an Android app's design system and iconography — Material Symbols drawables behind an AppIcons object, adaptive launcher icons with a monochrome layer, notification and splash icons, a Material 3 AppTheme with dynamic color and extended tokens, thin slot-based component wrappers, edge-to-edge…
swift-design-system-pro
Bootstraps or audits an Apple app's design system and iconography — SF Symbol facade and custom symbols, app icon (Icon Composer, Liquid Glass appearances), color/type/spacing/shape tokens, component styles, Liquid Glass adoption, and previews. Use when setting up the UI foundation of a new SwiftUI app, when…
android-accessibility-pro
Deep-reviews Android app accessibility — the TalkBack semantics tree (content descriptions, roles, merging, state, custom actions, live regions), Bluetooth assistive input (external keyboards, Switch Access, braille displays), and visual accessibility (contrast, dynamic text, color-independence, reduce motion). Use…
android-adaptive-layout-pro
Deep-reviews Android apps for tablet, foldable, and desktop-window readiness — window size class usage, canonical layouts (Material 3 adaptive scaffolds), fold posture handling, state survival across fold/unfold and resize, manifest orientation/resizability restrictions (ignored on large screens since Android 16), and…
design-to-ui
A workflow for turning Figma designs into native Android or iOS screens. Figma is a design tool; native output means Android Jetpack Compose or XML, and iOS SwiftUI or UIKit code that runs on those platforms.