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 agentmods add skills/vaadin/agent-skills/aura-themenpx skills add vaadin/agent-skills --skill aura-themegit clone --depth 1 https://github.com/vaadin/agent-skillsWrote 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/vaadin/agent-skills/aura-theme)<a href="https://agentmods.dev/skills/vaadin/agent-skills/aura-theme"><img src="https://agentmods.dev/badge/skills/vaadin/agent-skills/aura-theme.svg" alt="Measured on agentmods" 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.00098 | $0.04690 |
| Opus 5 | $0.00049 | $0.02345 |
| Sonnet 5 | $0.00020 | $0.00938 |
| Haiku 4.5 | $0.00010 | $0.00469 |
Grade A, and why
aura-theme 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 6d 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aura Theme Generator
Generate Vaadin Aura theme CSS files from free-form descriptions.
Workflow
- Interpret the user's description — identify the intended colors, mood, density, typography, layout, surface hierarchy, semantic brand colors, and any component-specific styling needs.
- Review relevant references based on what was identified in step 1:
- Always read references/property-values.md for valid property values and defaults.
- Select and read the most closely matching reference CSS files as idiomatic examples. Choose based on the interpreted style:
- references/cozy-paper.css — dark mode, emerald accent, spacious, flat surfaces, mixed content scheme, side nav + button patterns
- references/fresh-mint.css — same base config as cozy-paper, clean mint variant
- references/monochrome.css — neutral monochrome, auto color scheme, opaque overlays, monospace font, button border patterns
- references/night-operator.css — dark operator theme, same nav/button patterns as cozy-paper
- references/preset-sunset-glass.css — vibrant indigo, very rounded, heavy font weights, card elevation scoping
- Read references/components.md only when component-specific styling (e.g., Grid) was identified in step 1.
- Map each interpreted aspect to Aura properties using values from the references (always consider: surface level/opacity, app layout inset, font family, border radius; rarely: palette colors for semantic states; only when explicitly mentioned: component properties)
- Locate the styles.css file (default:
/src/main/resources/META-INF/resources/styles.css) - Name the file descriptively
- Create the theme CSS file in the same directory as styles.css
- Add an
@importstatement to styles.css to import the new theme file
What ships with it
7 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.
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.
- 6d ago First seen · 375 lines · 98 tokens per session scan A b522abb18ef8
aura-theme is a skill published in the GitHub repository vaadin/agent-skills (5 stars, last pushed 17d ago), licensed Apache-2.0. It adds 98 tokens to every session and 4,690 once invoked, about $0.0005 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-31.
Other skills, from other repositories
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.
waitlist-page
【模板: 等候名单页 / Waitlist】 【意图】为新产品 / 早鸟内测做一张极简等候页。 【布局】.
design-frontend-dev
Clean Impeccable frontend design skill. Use when the user wants to design, redesign, critique, audit, polish, harden, optimize, adapt, clarify, colorize, animate, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, onboarding, empty states…