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 byte5ai/palaia --skill lumegit clone --depth 1 https://github.com/byte5ai/palaiaWrote 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/byte5ai/palaia/lume)<a href="https://agentmods.dev/skills/byte5ai/palaia/lume"><img src="https://agentmods.dev/badge/skills/byte5ai/palaia/lume/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/byte5ai/palaia/lume"><img src="https://agentmods.dev/badge/skills/byte5ai/palaia/lume.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.00057 | $0.00603 |
| Opus 5 | $0.00028 | $0.00302 |
| Sonnet 5 | $0.00011 | $0.00121 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
lume-design 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.
What it actually says
Read the README.md file within this skill, and explore the other available files.
The system implements Lume — light-as-material — for Omadia UI, a generative desktop canvas application. The defining trait: every surface is a gradient pair (top + btm), every border is directional, accent renders as both fill and glow (two-stop, with a bright white-shifted inner core). Default palette is Lagoon (#1F8FA3). Typography is three-register: Geist (sans, structural) + Source Serif 4 (serif, prose) + Geist Mono (mono, data/code).
If creating visual artifacts (slides, mocks, throwaway prototypes, etc), copy colors_and_type.css and assets/ out of this folder and create static HTML files for the user to view. Add <html data-mode="light" data-accent="lagoon"> on the root.
If working on production code, you can copy assets and read the rules here to become an expert in designing with this brand.
Key files:
README.md— full design language (content tone, visual foundations, iconography, anti-patterns)colors_and_type.css— every design token, ready to importdocs/visual-spec.md— the normative source spec from the Omadia UI repodocs/visual-spec-preview-lume.html— visual reference rendered by the spec authorui_kits/omadia-canvas/— high-fidelity React recreation of core canvas screenspreview/— small per-token cards for the design-system tab
If the user invokes this skill without any other guidance, ask them what they want to build or design, ask some questions, and act as an expert designer who outputs HTML artifacts or production code, depending on the need. Hard constraints to remember:
- No logo —
omadiais muted body text, not a wordmark. - No emoji as chrome (agent-content emoji passes through unchanged).
- No drop shadows on cards. Shadows are reserved for modal-class surfaces.
- No status-pill cocktails or filled badges. Semantic states are text + 1px border, never block fills.
- No spinners. Skeletons or the button-in-flight dots are the only loading affordances.
- No "Welcome!" or branded empty states.
- The editor exception:
canvas-region,timeline,vector-pathget radius 0 and opaque (non-gradient) fills.
What ships with it
55 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/icons/README.md 932 B
- colors_and_type.css 16 KB
- docs/omadia-CONCEPT.md 58 KB
- docs/omadia-ui-README.md 3.7 KB
- docs/spec-preview-signal-block.html 9.3 KB
- docs/SPEC-v0.4-signal-handoff.md 3.7 KB
- docs/visual-spec-preview-lume.html 75 KB
- docs/visual-spec-preview-type.html 49 KB
- docs/visual-spec.md 68 KB
- docs/walkthroughs.md 32 KB
- fonts/README.md 2.4 KB
- IMPORT-NOTES.md 2.2 KB
- preview/_card.css 5.1 KB
- preview/brand-four-forces.html 3.5 KB
- preview/brand-prompt-bar.html 1.3 KB
- preview/brand-status-bar.html 1.2 KB
- preview/colors-accent-atelier.html 1.9 KB
- preview/colors-accent-lagoon.html 2.0 KB
- preview/colors-accent-petrol.html 1.9 KB
- preview/colors-glow-stack.html 1.4 KB
- preview/colors-signal-dark.html 3.2 KB
- preview/colors-signal.html 3.4 KB
- preview/colors-states.html 1.8 KB
- preview/colors-surfaces.html 1.8 KB
- preview/colors-text.html 1.4 KB
- preview/components-buttons.html 1.4 KB
- preview/components-choice.html 3.1 KB
- preview/components-inputs.html 953 B
- preview/components-list-selection.html 1.5 KB
- preview/components-progress.html 1.4 KB
- preview/components-skeleton.html 1012 B
- preview/components-wizard-steps.html 2.1 KB
- preview/motion-tokens.html 1.7 KB
- preview/radii-scale.html 3.2 KB
- preview/shadows-elevation.html 1.8 KB
- preview/spacing-scale.html 3.9 KB
- preview/type-body.html 955 B
- preview/type-display.html 946 B
- preview/type-mono.html 1.1 KB
- preview/type-prose.html 1.0 KB
- preview/type-registers.html 1.1 KB
- README.md 3.2 KB
- styles.css 726 B
- ui_kits/omadia-canvas/app.jsx 2.9 KB
- ui_kits/omadia-canvas/frame.jsx 1.6 KB
- ui_kits/omadia-canvas/index.html 2.7 KB
- ui_kits/omadia-canvas/kit.css 13 KB
- ui_kits/omadia-canvas/lucide-paths.js 7.2 KB runs code
- ui_kits/omadia-canvas/primitives.jsx 4.5 KB
- ui_kits/omadia-canvas/README.md 4.2 KB
- ui_kits/omadia-canvas/scene-dashboard.jsx 12 KB
- ui_kits/omadia-canvas/scene-empty.jsx 3.2 KB
- ui_kits/omadia-canvas/scene-wizard.jsx 12 KB
- ui_kits/omadia-canvas/scene-workspace.jsx 10 KB
- UPSTREAM-README.md 25 KB
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 · 32 lines · 57 tokens per session scan A b76239342215
lume-design is a skill published in the GitHub repository byte5ai/palaia (19 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 603 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
setup
A setup guide for session-recall, a tool that lets an agent search and reuse information from earlier conversations. It covers installation, language, local or cloud processing, and optional team sharing.
memx
Use when an agent needs to recall, save, inspect, or audit memX memories through the bundled MCP tools.
session-recall
Search the unified local history of past Claude Code, Codex, and Cursor sessions at the START of a task when the user references a prior bug, feature, decision, file, or piece of work. Use before assuming fresh context for prompts such as "remember when…", "we worked on…", "the X bug", "back to…", "what did we decide…
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
memory-to-skill
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under…