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 event4u-app/agent-config --skill laravel-pulsegit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/laravel-pulse)<a href="https://agentmods.dev/skills/event4u-app/agent-config/laravel-pulse"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/laravel-pulse/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/laravel-pulse"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/laravel-pulse.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.00043 | $0.01207 |
| Opus 5 | $0.00022 | $0.00603 |
| Sonnet 5 | $0.00009 | $0.00241 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
laravel-pulse 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
laravel-pulse
When to use
Use this skill when working with Laravel Pulse:
- Setting up the Pulse monitoring dashboard
- Configuring built-in recorders (slow queries, exceptions, queues, etc.)
- Creating custom Pulse cards and recorders
- Performance monitoring and alerting
Procedure: Set up Pulse
- Inspect current monitoring — Check
composer.json, existing telemetry packages, andconfig/for Pulse, Telescope, or Horizon already installed; identify gaps. - Install —
composer require laravel/pulse, publish config, run migrations. - Configure — Set up recorders in
config/pulse.php. - Add dashboard — Register route and authorize access.
- Verify — Visit
/pulsedashboard, confirm data is being recorded.
Installation
composer require laravel/pulse
php artisan vendor:publish --provider="Laravel\Pulse\PulseServiceProvider"
php artisan migrate
Dashboard
Access control
// PulseServiceProvider or Gate
Gate::define('viewPulse', function (User $user): bool {
return $user->isSuperuser();
});
Dashboard route
Pulse registers /pulse automatically. Customize in config/pulse.php:
'path' => 'pulse',
'middleware' => ['web', 'auth'],
Built-in cards
| Card | What it shows |
|---|---|
<livewire:pulse.servers /> |
CPU, memory, storage per server |
<livewire:pulse.usage /> |
Top users by request count |
<livewire:pulse.queues /> |
Queue throughput and wait times |
<livewire:pulse.slow-queries /> |
Slowest database queries |
<livewire:pulse.slow-requests /> |
Slowest HTTP requests |
<livewire:pulse.slow-jobs /> |
Slowest queued jobs |
<livewire:pulse.slow-outgoing-requests /> |
Slowest external HTTP calls |
<livewire:pulse.exceptions /> |
Most frequent exceptions |
<livewire:pulse.cache /> |
Cache hit/miss ratio |
Dashboard view
{{-- resources/views/vendor/pulse/dashboard.blade.php --}}
<x-pulse>
<livewire:pulse.servers cols="full" />
<livewire:pulse.usage cols="4" rows="2" />
<livewire:pulse.queues cols="4" />
<livewire:pulse.cache cols="4" />
<livewire:pulse.slow-queries cols="8" />
<livewire:pulse.exceptions cols="4" />
<livewire:pulse.slow-requests cols="6" />
<livewire:pulse.slow-jobs cols="6" />
</x-pulse>
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 · 172 lines · 43 tokens per session scan A a739820abfbf
laravel-pulse 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,207 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-03.
Other skills, from other repositories
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
Concurrency Testing Patterns
Testing concurrent code including race condition detection, deadlock prevention, thread safety verification, and parallel execution correctness.
kiro-verify-completion
Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
monte-carlo-performance-diagnosis
Diagnoses pipeline performance issues -- slow jobs, expensive queries, latency trends -- using Monte Carlo's cross-platform observability. Uses a tiered investigation approach: discover problems, bridge to affected tables, then drill into root causes. Activates when a user asks about slow pipelines, expensive queries…