Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/event4u-app/agent-confignpx agentmods add skills/event4u-app/agent-config/livewireWrote 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/event4u-app/agent-config/livewire)<a href="https://agentmods.dev/skills/event4u-app/agent-config/livewire"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/livewire/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/event4u-app/agent-config/livewire"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/livewire.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.00043 | $0.01455 |
| Opus 5 | $0.00022 | $0.00727 |
| Sonnet 5 | $0.00009 | $0.00291 |
| Haiku 4.5 | $0.00004 | $0.00145 |
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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
livewire
Grounded stack guidance: pull idiomatic Blade/UI Do/Don't + docs URLs via
./scripts-run <skills-root>/corpus-grounding/scripts/ground search --manifest <skills-root>/design-intelligence/data/manifest.json --stack laravel "<topic>"(UI-scoped corpus). Seedesign-intelligence.
Positioning — dispatched, not standalone
livewire is the apply-step executor for the Livewire stack. It is
invoked by directives/ui/apply.ts
once the design brief is locked, and revisited by review.ts /
polish.ts during the design-review loop. It does not own the
flow, does not drive the audit, and does not lock the design.
| Concern | Owner |
|---|---|
| Audit + token inventory (mandatory pre-step) | existing-ui-audit |
| Design brief (layout / states / microcopy) | directives/ui/design.ts |
| Universal design heuristics | fe-design |
| Static Blade partials inside the view | blade-ui |
| Flux primitives inside the view | flux |
When to use
Cite this skill when:
state.stack.frontend == "livewire"anddirectives/ui/apply.tsdispatches to this skill- Editing or creating Livewire components — reactive state, forms, tables, real-time updates
Do NOT use when:
- Static Blade views with no interactivity (use
blade-uiskill) - Flux UI primitives (use
fluxskill —livewirecomposes Flux internally) - Driving the full UI flow yourself — that is the
directives/ui/orchestrator
Procedure: Create a Livewire component
Step 0: Inspect
- Detect Livewire version —
composer.jsonforlivewire/livewire.- v3:
#[Layout],#[Title], property attributes. - v2:
$layout,$listeners, method-based hooks.
- v3:
- Check existing components —
app/Livewire/orapp/Http/Livewire/. - Check views —
resources/views/livewire/.
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 · 149 lines · 43 tokens per session scan A 51948462c2dd
livewire is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,455 once invoked, about $0.0002 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
devlab-contract-web-server
A guide for agreeing on how a separate frontend and backend communicate through APIs. An API contract defines field types, optional values, data formatting, error codes, and which configuration belongs on each side.
fec-data-fetching
A frontend guide for handling data that comes from a server, including typed requests, caching, refreshing, pagination, and updates. Server state means data owned by an API rather than by a page’s local controls.
Appsmith Open Source Internal Tools and Admin Panel Builder
Appsmith is an open-source platform for building internal tools, dashboards, and admin panels on top of databases and APIs. It is well suited to operational workflows where agents or developers need a fast way to stand up interfaces for support, ops, analytics, or back-office tasks.
audit-fe-api
Audit frontend API calls against backend implementation for contract alignment and network shape. Use when "API audit", "FE-BE contract", or "review frontend API integration". Live 4xx/5xx reproduction → debug-fe-be-integration.
backend-realtime
Implement real-time features using WebSockets, Supabase Realtime, Server-Sent Events, and live data. Use when user wants "real-time", "live updates", "WebSocket", "notifications", "chat", "collaborative", "presence", "live data", or "instant sync".
api-integration
When connecting a component to a REST API, handling loading/error states, or implementing optimistic updates.