Livewire PowerGrid is a Laravel package for creating configurable data tables in web applications. Laravel developers use it for tables with searching, filtering, sorting, editing, bulk actions, pagination, and data export. The catalogue add-ons support work with this package.
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 Power-Components/livewire-powergrid --skill create-powergrid-plugingit clone --depth 1 https://github.com/Power-Components/livewire-powergridWrote 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/power-components/livewire-powergrid/create-powergrid-plugin)<a href="https://agentmods.dev/skills/power-components/livewire-powergrid/create-powergrid-plugin"><img src="https://agentmods.dev/badge/skills/power-components/livewire-powergrid/create-powergrid-plugin/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/power-components/livewire-powergrid/create-powergrid-plugin"><img src="https://agentmods.dev/badge/skills/power-components/livewire-powergrid/create-powergrid-plugin.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.00031 | $0.01055 |
| Opus 5.5 | $0.00012 | $0.00422 |
| Sonnet 5.5 | $0.00006 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade A, and why
create-powergrid-plugin 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 1mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
Scaffold a complete external PowerGrid plugin in the user's project (NOT in the package).
When to use me
- A new interactive column behavior is needed (e.g., selectable, colorpicker, rating)
- The behavior requires its own Blade view and/or Alpine.js component
- The plugin needs to respond to user interactions via Livewire events
Quick Overview
Plugins are created in the user's project at app/PowerGrid/Plugins/{PluginName}/.
They do NOT require modifying the PowerGrid package.
Files to create:
app/PowerGrid/Plugins/{PluginName}/{PluginName}Plugin.php- Plugin classapp/PowerGrid/Plugins/{PluginName}/index.blade.php- Blade templateapp/PowerGrid/Plugins/{PluginName}/index.js- Alpine.js componentapp/Providers/PowerGridPluginServiceProvider.php- ServiceProvider
Files to modify:
bootstrap/providers.php- Register the ServiceProviderapp/Providers/AppServiceProvider.php- Add plugin toPowerGrid::plugins([...])- User's PowerGrid component - Add column + hook method
Critical Rules
- Create plugins in user's project, never in the powergrid package
- ServiceProvider must call
boot()and register view namespace withloadViewsFrom() - Alpine.js dispatch must use array format:
[field, id, value](NOT object{field, id, value}) - Render initial values server-side with
@foreach/@selected()- do NOT usex-modelfor initial state - Model
$fillablemust include the field being updated - No proxy method needed -
pgPluginListenerin Listeners.php handles routing generically - Theme-aware markup uses tokens, not
instanceof. Contribute classes viaPluginBase::themeTokens(); resolve views withtheme_view($alias)and fall back topowergrid-plugins::{PluginName}.themes.*.
Theme-aware plugins
Plugins can inject CSS-class tokens and ship theme-aware Blade without theme conditionals.
PluginBase::themeTokens() is merged into every theme in Theme::resolveTokens() (after the theme's own section methods, before config('livewire-powergrid.theme_overrides')). It is a raw array (not run through HasProperties::toArray()), so keys must already be snake_cased. The tabs group (list / tab / tab_active / tab_inactive / badge / badge_active / badge_inactive / optional view) is the first real example of a plugin-shaped token surface:
What ships with it
1 file 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.
- 1mo ago Changed · +40 lines b0fd7b588e7e
- 1mo ago First seen · 56 lines · 31 tokens per session scan A 2739266cd660
create-powergrid-plugin is a skill published in the GitHub repository Power-Components/livewire-powergrid (1,693 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 1,055 once invoked, about $0.0001 per session on Opus 5.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
laravel-upgrade
Upgrade a Laravel application across major versions safely (Laravel 8 -> 9 -> 10 -> 11 -> 12 -> 13), one hop at a time. Use when upgrading Laravel, when a composer update fails after a major bump, when deciding whether to hop versions by hand or pay for Laravel Shift, or when something compiled fine but broke at…
filament-plugin-development
Build and publish custom Filament plugins (Filament is the Laravel admin-panel framework). Use when creating a Filament plugin/package, implementing the Plugin contract, scaffolding from the plugin skeleton, registering assets/resources/pages/render-hooks, making a configurable plugin, testing it, or publishing to…
owl-admin-devtools-generator
A development guide for Owl Admin, a Laravel-based administration system, covering its code generator, API templates, relationships, and visual pages.
laravel
Use when building or extending a Laravel 11/12 app — Eloquent models, migrations and relationships, routing with controllers and Form Requests, queues and background jobs, framework-native security (validation, mass-assignment, policies, signed URLs, rate limiting), and Pest/PHPUnit feature tests. NOT pure PHP…
php-expert
Expert-level PHP development with PHP 8+, Laravel, Composer, and modern best practices. Use when the user mentions Laravel, Composer, Symfony, PHPUnit, or PSR standards, or when the task involves PHP 8+ Features, Object-Oriented PHP, Modern PHP, or Constructor Property Promotion.
php-laravel
Use this skill when building Laravel applications — MVC structure, Eloquent ORM, service layer, validation, queues, and testing. This skill enforces: thin controllers, service layer for business logic, Eloquent best practices with eager loading, form request validation, and queue job structure. Requires Laravel 10+ or…