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 nasrulhazim/claude --skill livewire-fluxgit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/nasrulhazim/claude/livewire-flux)<a href="https://agentmods.dev/skills/nasrulhazim/claude/livewire-flux"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/livewire-flux/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/nasrulhazim/claude/livewire-flux"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/livewire-flux.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.00225 | $0.05881 |
| Opus 5 | $0.00112 | $0.02941 |
| Sonnet 5 | $0.00045 | $0.01176 |
| Haiku 4.5 | $0.00022 | $0.00588 |
Grade A, and why
livewire-flux 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 12d 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 — 833 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Livewire 4 + Flux UI Component Scaffolder
Scaffold production-ready Livewire 4 components using Flux UI primitives — never raw Alpine when Flux already has a component. Covers forms, data tables, modals, notifications, file uploads, and Spatie package integrations.
Kickoff Baseline
This skill assumes the project already has:
- Laravel 11+
- Livewire 4 installed and configured
- Flux UI installed with dark mode support
- Tailwind CSS 4+
If the user hasn't set these up yet, point them to the official installation docs before proceeding.
Command Reference
| Command / Request | Description |
|---|---|
/livewire component <Name> |
Scaffold a Livewire component (full-class or Volt) |
/livewire form <Model> |
Generate a Flux-based form for a model with validation |
/livewire table <Model> |
Generate a data table with sorting, filtering, pagination |
/livewire patterns |
Show Livewire 4 + Flux best practices and anti-patterns |
1. Component Scaffolding
1.1 Full-Class Components
When the user asks for a component, generate both the class and Blade view.
Class file (app/Livewire/{Name}.php):
<?php
namespace App\Livewire;
use Livewire\Component;
use Livewire\Attributes\Layout;
use Livewire\Attributes\Title;
#[Layout('components.layouts.app')]
#[Title('Page Title')]
class UserIndex extends Component
{
public function render()
{
return view('livewire.user-index');
}
}
Blade view (resources/views/livewire/{name}.blade.php):
<div>
{{-- Content using Flux components --}}
</div>
1.2 Volt Single-File Components
When the user requests Volt or a simpler component, use single-file format:
<?php
use Livewire\Volt\Component;
new class extends Component {
public string $name = '';
public function save(): void
{
// ...
}
}; ?>
<div>
<flux:input wire:model="name" label="Name" />
<flux:button wire:click="save">Save</flux:button>
</div>
What ships with it
3 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.
- 12d ago First seen · 833 lines · 225 tokens per session scan A 9747ddc9c1cd
livewire-flux is a skill published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 9d ago), licensed MIT. It adds 225 tokens to every session and 5,881 once invoked, about $0.0011 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-30.
Other skills, from other repositories
symfony-backend
Use this skill when building Symfony backend applications — bundles, Doctrine ORM, Twig templates, Flex recipes, Messenger component. This skill enforces: service container autowiring, proper bundle structure, Doctrine mapping conventions, Flex-driven configuration. Do NOT use for: Laravel projects, WordPress plugins…
electrik-slate
Build Laravel Blade UI with Electrik Slate 3.x and optional slate-blocks. Use when writing x-slate or x-slate-block components, Livewire forms, tokens, toasts, blocks, or when the user mentions Slate, electrik/slate, electrik/slate-blocks, or slate.electrik.dev.
laravel-vite
Complete Vite bundling for Laravel - assets, HMR, SSR, frameworks, optimization. Use when configuring frontend build pipeline.
laravel:blade-components-and-layouts
Compose UIs with Blade components, slots, and layouts; keep templates pure and testable.
spatie-guidelines
Spatie's PHP, Laravel, JavaScript and Vue coding guidelines and conventions. Use when writing or reviewing PHP, Laravel, JavaScript, or Vue code for Spatie projects or packages. Covers code style, type declarations, docblocks, control flow, naming, routing, controllers, Blade, validation, comments, testing (Pest)…
livewire-4
Build Livewire 4 components and applications. Use when creating reactive Laravel interfaces, single-file components, multi-file components, page components, forms, actions, or any Livewire-based UI. Triggers include "Livewire component", "wire:model", "wire:click", building interactive Laravel UIs, or working with…