What is superpowers-sage:livewire-debugger?

A debugging guide for Livewire components in Sage and Acorn PHP projects. It checks the component's PHP class, its Blade template, and the browser bindings that connect them.

Use it to diagnose Livewire mounting failures, input updates, button actions, form submissions, events, Alpine.js conflicts, stale computed values, and missing components.

It helps find why a component will not load, update, run an action, or send an event. It points to common causes such as missing scripts, incorrect namespaces, outdated event syntax, and CSRF or route errors.

superpowers-sage:livewire-debugger — Agent for Claude Code by hekivo

Install

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.

Clone the repo

git clone --depth 1 https://github.com/hekivo/superpowers-sage

Made for: Claude Code.

Or install superpowers-sage, the plugin that ships this one along with the rest of its 36 skills, 3 commands, 11 agents, 7 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/hekivo/superpowers-sage/livewire-debugger/github.svg)](https://agentmods.dev/agents/hekivo/superpowers-sage/livewire-debugger)

Your own site

<a href="https://agentmods.dev/agents/hekivo/superpowers-sage/livewire-debugger"><img src="https://agentmods.dev/badge/agents/hekivo/superpowers-sage/livewire-debugger/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/hekivo/superpowers-sage/livewire-debugger"><img src="https://agentmods.dev/badge/agents/hekivo/superpowers-sage/livewire-debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 193 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 995 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00193	$0.00995
Opus 5.5	$0.00077	$0.00398
Sonnet 5.5	$0.00039	$0.00199
Haiku 4.5	$0.00019	$0.00100

Measured 1mo ago against content hash c2308efb75df, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

superpowers-sage:livewire-debugger 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.

agents/livewire-debugger.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Livewire debugging specialist for Sage/Acorn projects. Diagnose the root cause and provide a concrete fix.

MANDATORY: All output (diagnostic reports, code fixes) MUST be written in en-US.

Diagnostic Categories

Symptom	First Check
Component doesn't mount	`@livewireScripts` in layout? Namespace registered?
Property doesn't update on input	`wire:model.live` needed in Livewire v3 (`.lazy` is v2)
Action not firing	`wire:click` on correct element? Method `public`?
419 CSRF error	Route in `web` middleware group? Session active?
403 / 404 on `/livewire/update`	`web` middleware applied to route?
`emit` not received	Livewire v3 uses `dispatch()` not `emit()`
Alpine conflict	`wire:ignore` on Alpine-managed element?
Computed property stale	`#[Computed]` attribute present (v3)?
Component not found	Class in correct namespace? `lando wp acorn livewire:discover`?

Process

Step 1 — Locate the component

Find:

app/Http/Livewire/<ComponentName>.php
resources/views/livewire/<component-name>.blade.php

Step 2 — Audit the component class

Read the PHP class. Check:

All wire:model-bound properties are public
mount() receives correct injected parameters
Actions are public methods with correct names
Livewire v3: dispatch() not emit(); #[Computed] attribute for computed props
No protected/private properties bound with wire:model

Step 3 — Audit the Blade view

Read the view. Check:

wire:model.live="property" for real-time updates in v3 (not bare wire:model)
wire:click="methodName" — method name matches class exactly
wire:submit.prevent on forms
No duplicate root element id attributes
Alpine x-data on a child element, not the Livewire root (unless using @entangle)

Step 4 — Check layout for asset injection

Grep: livewireScripts in resources/views/layouts/
Grep: livewireStyles in resources/views/layouts/

Livewire v3 alternative: <livewire:scripts /> tag. One or the other must be present.

Read the full file on GitHub · 110 lines

Changes

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 First seen · 110 lines · 193 tokens per session scan A c2308efb75df

Subscribe to this mod's changes

superpowers-sage:livewire-debugger is an agent published in the GitHub repository hekivo/superpowers-sage (14 stars, last pushed 8d ago), licensed MIT. It adds 193 tokens to every session and 995 once invoked, about $0.0008 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.

Debugging Languages PHP client-hekivo tier-shared

laravel-debugger

Expert Laravel debugger specializing in diagnosing complex issues, analyzing Laravel-specific problems, and systematic problem-solving. Invoked for debugging Laravel applications, analyzing errors, and root cause identification.

iSerter/laravel-claude-agents · 39 tokens

phpstan-error-resolver

À utiliser de manière proactive pour analyser et corriger systématiquement les erreurs PHPStan niveau 9 dans les projets PHP/Symfony. Spécialiste pour résoudre les problèmes de types stricts, annotations generics, array shapes et collections Doctrine.

atournayre/claude-marketplace · 56 tokens

superpowers-sage:livewire-debugger