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-notificationsgit 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-notifications)<a href="https://agentmods.dev/skills/event4u-app/agent-config/laravel-notifications"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/laravel-notifications/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-notifications"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/laravel-notifications.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.00032 | $0.01142 |
| Opus 5 | $0.00016 | $0.00571 |
| Sonnet 5 | $0.00006 | $0.00228 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
laravel-notifications 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
laravel-notifications
When to use
Use this skill when sending notifications to users or external systems:
- Email, Slack, SMS, or database notifications
- Custom notification channels
- On-demand notifications (to non-user recipients)
- Notification preferences and opt-out logic
For Mailables (complex email templates, attachments), see laravel-mail.
Procedure: Create a notification
- Inspect existing notifications — Read
app/Notifications/and the notifiable models for current channels, queue defaults, and per-user preferences. - Generate class —
php artisan make:notification InvoiceCreated. - Choose channels — Mail, database, Slack, or custom. Implement
via(). - Build content — Implement
toMail(),toArray(), etc. for each channel. - Queue it — Add
ShouldQueueinterface for non-blocking delivery. - Verify — Send test notification, confirm delivery on all channels.
Example
php artisan make:notification InvoiceCreated
class InvoiceCreated extends Notification implements ShouldQueue
{
use Queueable;
public function __construct(
private readonly Invoice $invoice,
) {}
/** @return array<int, string> */
public function via(object $notifiable): array
{
return ['mail', 'database'];
}
public function toMail(object $notifiable): MailMessage
{
return (new MailMessage())
->subject('New Invoice #' . $this->invoice->getNumber())
->greeting('Hello ' . $notifiable->getName())
->line('A new invoice has been created.')
->action('View Invoice', url('/invoices/' . $this->invoice->getId()))
->line('Thank you for your business.');
}
/** @return array<string, mixed> */
public function toArray(object $notifiable): array
{
return [
'invoice_id' => $this->invoice->getId(),
'amount' => $this->invoice->getAmount(),
];
}
}
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 · 180 lines · 32 tokens per session scan A 3b3375fa54dc
laravel-notifications is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,142 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
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
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…
api-doc-generator
Generate API documentation from source code, supporting REST APIs, GraphQL, and various documentation formats.
telnyx-ai-inference-curl
Access Telnyx LLM inference APIs, embeddings, and AI analytics for call insights and summaries. This skill provides REST API (curl) examples.
telnyx-ai-assistants-curl
AI voice assistants with custom instructions, knowledge bases, and tool integrations.
telnyx-email-domains-curl
Manage email sending domains, verify DNS records (SPF, DKIM, DMARC, MX), check domain health, and configure domain-level webhooks for delivery events.