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 agentmods add instructions/power-components/livewire-powergrid/claude-mdgit 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/instructions/power-components/livewire-powergrid/claude-md)<a href="https://agentmods.dev/instructions/power-components/livewire-powergrid/claude-md"><img src="https://agentmods.dev/badge/instructions/power-components/livewire-powergrid/claude-md.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 | $0.01304 | $0.01304 |
| Opus 5 | $0.00652 | $0.00652 |
| Sonnet 5 | $0.00261 | $0.00261 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
livewire-powergrid CLAUDE.md 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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- livewire-powergrid GEMINI.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerGrid 7.x AI Guidelines
This document outlines the architectural guidelines for AI agents working with PowerGrid 7.x.
1. Core Principles
The 7.x version prioritizes simplicity, an adaptable native skeleton, and independent test components, discarding legacy dependencies.
- PHP: 8.3+
- Livewire: 4.0+
- Tailwind CSS: 4.x+
- Removed Legacy Dependencies: Bootstrap, third-party select integrations, Lazy components, and Pulse files.
- New Required Package:
power-components/partials(imported locally).
2. Architecture & Theming
- Theme classes (
src/Themes): Tailwind (root), DaisyUI and Flux extend it viaparentTheme. - Section-based authoring: A theme exposes per-section methods (
layout(),header(),table(),footer(),cols(),tabs(), plusfilter()/editable()/toggleable()), each returning a token slice; they are auto-merged bythemeTokenMethods().struct()only setsbaseView(). Write a slice as a plain nested array (6.x style) or with the fluent builder via thesection()helper.ArrayThemebuilds a whole theme from an array. - Selection & registry:
config('livewire-powergrid.theme')accepts a registered name ('tailwind'|'daisyui'|'flux') or an FQCN, resolved throughPowerGridManager::$themes/registerTheme(). - No-code overrides:
config('livewire-powergrid.theme_overrides')merges token overrides at the highest precedence — restyle any token without a Theme class. - Absolute Separation: HTML structure is separated from visual styles; classes live in tokens read by the
theme()helper.
3. Views
- No Theme Conditionals: Do not use logic like
@if($theme == 'bootstrap')in Blade files. - Micro-files Strategy: Table views are single-purpose micro-files under
resources/views/components/structure/(e.g.table.blade.php,partials/tbody.blade.php,table/row.blade.php). - Token-driven, minimal overrides: A theme ships a blade only when the HTML structure genuinely differs; class-only differences live in tokens. DaisyUI ships zero blades (fully token-driven, inheriting Tailwind's views); Flux keeps blades that use
<flux:*>components. - Helpers: Read tokens with
theme('key')(or@theme('key')) and resolve views withtheme_view('alias').
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.
- today Changed · +4 lines · +306 tokens per session cda22356564d
- 5d ago First seen · 96 lines · 998 tokens per session scan A e6cd4f7ca2b6
livewire-powergrid CLAUDE.md is an instructions file published in the GitHub repository Power-Components/livewire-powergrid (1,693 stars, last pushed today), licensed MIT. It adds 1,304 tokens to every session, about $0.0065 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 instructions, from other repositories
real-estate-laravel copilot-instructions.md
Instructions for liberusoftware/real-estate-laravel, covering lerd, a local php development environment, architecture, dns modes, mcp tools and key conventions.
laravel AGENTS.md
AGENTS.md instructions for laravel/laravel, covering laravel application, prerequisites and agent setup.
laravel CLAUDE.md
Claude Code instructions for laravel/laravel, covering laravel application, prerequisites and agent setup.
LarAgent AGENTS.md
Instructions for MaestroError/LarAgent, covering purpose, key principles, planning, executing plan and testing.
laravel-mcp-server AGENTS.md
Instructions for opgginc/laravel-mcp-server, covering common commands, testing and quality assurance, mcp tool development, mcp notification development and configuration publishing.
aura-ui AGENTS.md
Instructions for BlueStarSystem/aura-ui, covering agents.md — aura ui, what this is, how to use components, livewire integration and accessibility (do not regress).