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.
git clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/commands/nasrulhazim/claude/upgrade-livewire)<a href="https://agentmods.dev/commands/nasrulhazim/claude/upgrade-livewire"><img src="https://agentmods.dev/badge/commands/nasrulhazim/claude/upgrade-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/commands/nasrulhazim/claude/upgrade-livewire"><img src="https://agentmods.dev/badge/commands/nasrulhazim/claude/upgrade-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.00000 | $0.02545 |
| Opus 5 | $0.00000 | $0.01273 |
| Sonnet 5 | $0.00000 | $0.00509 |
| Haiku 4.5 | $0.00000 | $0.00254 |
Grade A, and why
upgrade-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 9d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Livewire 3 to 4 Upgrade Assistant
You are a specialized assistant for upgrading Laravel Livewire from version 3 to version 4.
Step 1: Identify Upgrade Type
CRITICAL: Before any upgrade, determine if this is an APPLICATION or PACKAGE.
Detection Checklist
| Check | Application | Package |
|---|---|---|
composer.json type field |
"type": "project" |
"type": "library" |
Has public/index.php |
Yes | No |
Has app/Http/ directory |
Yes | No |
Has src/ directory |
No | Yes |
Uses PackageServiceProvider |
No | Usually |
| Published on Packagist | Rarely | Yes |
Quick Detection Commands
# Check composer.json type
grep '"type"' composer.json
# Check for application indicators
ls public/index.php 2>/dev/null && echo "APPLICATION" || echo "Might be PACKAGE"
# Check for package indicators
ls src/ 2>/dev/null && echo "Might be PACKAGE" || echo "Might be APPLICATION"
Step 2: Follow the Correct Workflow
For Applications
- Update composer.json: Change
"livewire/livewire": "^3.0"to"livewire/livewire": "^4.0" - Run composer update:
composer update livewire/livewire --with-all-dependencies - Clear caches:
php artisan optimize:clear - Run tests:
composer test - Update deprecated patterns (if any)
For Packages
- Update composer.json: Change to
"livewire/livewire": "^3.0 || ^4.0" - Add version-aware component registration (see below)
- Test with both Livewire 3 and 4
- Update CI matrix for dual-version testing
Quick Reference
Backward Compatible (No Changes Needed)
These patterns work identically in Livewire 3 and 4:
// Attributes
#[Layout('layouts.app')]
#[Url]
#[Validate('required')]
#[Computed]
#[On('event-name')]
// Event dispatching
$this->dispatch('event-name');
$this->dispatch('event-name', data: $value);
// Validation
protected array $rules = ['name' => 'required'];
// URL state
protected $queryString = ['search' => ['except' => '']];
// Traits
use WithPagination;
use WithFileUploads;
// Lifecycle
public function mount() {}
public function updatedPropertyName() {}
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.
- 9d ago First seen · 335 lines · 0 tokens per session scan A e0afae54d7f8
upgrade-livewire is a command published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,545 tokens. 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 commands, from other repositories
generate-controller
Generate a Laravel controller following best practices.
laravel-attributes
Use first-party PHP attributes for controllers, jobs, and models (Laravel 13+); use the laravel:php-attributes skill exactly as written.
laravel-form-requests
Extract validation to Form Requests; use the laravel:form-requests skill exactly as written.
sync-sibling-php-repos
Synchronize sibling PHP repositories by propagating relevant commits from the current repository.
php-expert
Invoke the PHP expert skill for Laravel, WordPress, and Drupal.
infolist
Create FilamentPHP v4 infolists with entries, layouts, and sections for read-only view pages.