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 majdghithan/agent-skills --skill livewiregit clone --depth 1 https://github.com/majdghithan/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/majdghithan/agent-skills/livewire)<a href="https://agentmods.dev/skills/majdghithan/agent-skills/livewire"><img src="https://agentmods.dev/badge/skills/majdghithan/agent-skills/livewire.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.00119 | $0.01114 |
| Opus 5 | $0.00060 | $0.00557 |
| Sonnet 5 | $0.00024 | $0.00223 |
| Haiku 4.5 | $0.00012 | $0.00111 |
Grade A, and why
livewire 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 8d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel Livewire (v1 - v4)
Livewire builds reactive UIs with a PHP class + Blade view and no dedicated JS. Its behavior has flipped in important ways between majors - the same wire:model is real-time on v1/v2, deferred on v3, and non-bubbling on v4. So: detect the version, then apply that version's rules.
Step 1 - Detect the installed version FIRST
composer show livewire/livewire | grep -i '^versions' # resolved version
grep '"livewire/livewire"' composer.json # the constraint (^1/^2/^3/^4)
php artisan about | grep -i livewire # if available
Map to major 1.x / 2.x / 3.x / 4.x. Fresh install -> default to latest stable and confirm. Can't tell -> ask, don't guess.
Step 2 - Load the matching reference
| Version | Era (one-liner) | Reference |
|---|---|---|
| v1 (Feb 2020) | First stable; Alpine separate; wire:model live by default |
references/livewire-v1.md |
| v2 (Sep 2020) | $wire + @entangle, wire:model.defer, $rules, scoped events |
references/livewire-v2.md |
| v3 (Aug 2023) | App\Livewire, Alpine bundled, wire:model deferred by default, dispatch(), PHP attributes, wire:navigate |
references/livewire-v3.md |
| v4 (Jan 2026) | Single-file & island components, parallel updates, .async, wire:sort/intersect/ref, Route::livewire() |
references/livewire-v4.md |
Step 3 - For upgrades, load the matching guide
| Path | Guide | The headline break |
|---|---|---|
| v1 -> v2 | references/upgrades/v1-to-v2.md |
$updatesQueryString->$queryString, routing, {{ $slot }} |
| v2 -> v3 | references/upgrades/v2-to-v3.md |
wire:model now deferred (add .live); emit->dispatch; namespace move; Alpine bundled |
| v3 -> v4 | references/upgrades/v3-to-v4.md |
wire:model stops bubbling (add .deep); .blur/.change no longer request (add .live); self-closing tags; Route::livewire() |
The two behavior flips to burn into memory
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.
- 8d ago First seen · 54 lines · 119 tokens per session scan A 77cc311e279d
livewire is a skill published in the GitHub repository majdghithan/agent-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 119 tokens to every session and 1,114 once invoked, about $0.0006 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
olakunlevpn-filament-skills
Use when writing, reviewing, or refactoring Filament PHP v5 code -- resources, forms, tables, infolists, actions, widgets, panels, relation managers, multi-tenancy, testing, or plugin development. Always apply these standards to all Filament work.
laravel-livewire
Build dynamic, reactive Laravel applications using Livewire. Create real-time interfaces without writing JavaScript for SPA-like experiences.
create-powergrid-plugin
Create a complete PowerGrid plugin from scratch, including PHP class, Column macro, Blade view, Alpine.js component, and registration.
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.
build-me
Implement a solution write-up (typically the markdown file produced by /solve-me) in this Laravel project, following existing project patterns and Laravel best practices. Cuts the work into commits itself, writes the commit plan to docs/build/ .md, and gets the developer's approval before writing any code. Then builds…