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 leMaur/livewire-flux-mcp --skill fluxui-developmentgit clone --depth 1 https://github.com/leMaur/livewire-flux-mcpWrote 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/lemaur/livewire-flux-mcp/fluxui-development)<a href="https://agentmods.dev/skills/lemaur/livewire-flux-mcp/fluxui-development"><img src="https://agentmods.dev/badge/skills/lemaur/livewire-flux-mcp/fluxui-development/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/lemaur/livewire-flux-mcp/fluxui-development"><img src="https://agentmods.dev/badge/skills/lemaur/livewire-flux-mcp/fluxui-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00143 | $0.01606 |
| Opus 5 | $0.00072 | $0.00803 |
| Sonnet 5 | $0.00029 | $0.00321 |
| Haiku 4.5 | $0.00014 | $0.00161 |
Grade A, and why
fluxui-development 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flux UI Development
Flux UI is a component library for Livewire built with Tailwind CSS. Use Flux components when one exists. Fall back to standard Blade components only when no Flux component covers the need.
Documentation
This project has the flux-docs MCP server available. It reads
fluxui.dev on demand, so it always reflects the components that exist
today and knows which ones are Pro-gated.
Look Flux things up with flux-docs first. Do not answer from memory, and do not treat
any component list written into a guideline or skill (including this one) as authoritative.
| Question | Tool | Notes |
|---|---|---|
| Which components exist? Is X free or Pro? | list_flux_components |
tier: 'free' | 'pro' | 'all', annotates each result [Free] / [Pro] |
| What props/slots/variants does X take? | fetch_flux_docs |
component: 'button' — returns the page plus its reference section |
| Which layouts exist? | list_flux_layouts |
v2 only |
| How is layout X structured? | fetch_flux_docs |
layout: 'header' |
| What icons can I use, and what is the exact name? | list_flux_component_icons |
variant and search filters |
If flux-docs is unavailable, say so and stop — do not guess component or prop names.
Boost's search-docs tool is a reasonable secondary source for prose and Livewire-side
questions, but flux-docs is the authority on what a Flux component actually accepts.
Workflow
- Discover —
list_flux_componentsto confirm the component exists and get its slug. - Check the tier — if it comes back
[Pro], confirm the project has Flux Pro before building on it.fetch_flux_docsalso prepends a[NOTICE] This is a Flux Pro componentline for Pro pages. - Fetch the API —
fetch_flux_docsfor the component or layout. Read the reference section; that is where props, slots and variants live. - Resolve icons —
list_flux_component_iconswith asearchterm. Never invent an icon name. - Build the Blade markup.
- Verify — component renders, interactive states work, layout holds on mobile.
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 · 156 lines · 143 tokens per session scan A aecd72579dab
fluxui-development is a skill published in the GitHub repository leMaur/livewire-flux-mcp (9 stars, last pushed yesterday), licensed MIT. It adds 143 tokens to every session and 1,606 once invoked, about $0.0007 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
powergrid-theme
Create or update a PowerGrid v7 theme using the Theme abstract class, per-section token methods (layout/header/table/footer/cols/tabs plus filter/editable/toggleable), config themeoverrides, or ArrayTheme.
upgrade-theme-v6-to-v7
Migrates a v6 Theme class to the v7 architecture: a tiny struct() plus per-section token methods (layout/header/table/footer/cols/tabs + filter/editable/toggleable) with parentTheme inheritance.
sfcc-sfra-scss
Best practices for styling and theming SFRA storefronts using SCSS. Use when asked to create style overrides, theming, responsive layouts, or CSS customizations in SFCC.
shadcn-sveltekit-design
Use when building, redesigning, beautifying, or refactoring SvelteKit pages and reusable components with shadcn-svelte, Bits UI, or the shadcn-svelte MCP. Trigger on landing pages, dashboards, marketing sites, app shells, forms, navbars, tables, dialogs, responsive layouts, theming, icon selection, and requests to…
orchardcore-asset-manager
Skill for building, watching, hosting, and copying frontend assets in Orchard Core 3.0 with the Assets Manager. Covers Assets.json actions, Concurrently, Parcel, Vite, Webpack, Yarn workspace setup, migration from Gulp, common commands, package dependencies, and troubleshooting. Use this skill for framework-only…
orchardcore-crestapps-resources
Skill for CrestApps resource-management extensions in Orchard Core. Covers the shared registered scripts and stylesheets, local asset and CDN fallback behavior, resource names, dependency consumption, and safe Razor registration. Use this skill when requests mention CrestApps shared resources, Orchard Core resource…