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-schedulinggit 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-scheduling)<a href="https://agentmods.dev/skills/event4u-app/agent-config/laravel-scheduling"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/laravel-scheduling/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-scheduling"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/laravel-scheduling.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.00028 | $0.01409 |
| Opus 5 | $0.00014 | $0.00705 |
| Sonnet 5 | $0.00006 | $0.00282 |
| Haiku 4.5 | $0.00003 | $0.00141 |
Grade A, and why
laravel-scheduling 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 4d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
laravel-scheduling
When to use
Use this skill when scheduling recurring tasks:
- Artisan command scheduling
- Job dispatching on a schedule
- Closure-based scheduled tasks
- Overlap prevention and maintenance mode handling
Procedure: Create a scheduled task
- Inspect existing schedule — Read
routes/console.php(Laravel 11+) orapp/Console/Kernel.phpto identify current cadence, overlap-prevention patterns, and output handling. - Pick frequency and concurrency policy — Choose a frequency helper (see table) or a cron expression; decide whether
withoutOverlapping()/onOneServer()is required. - Register the task — Add the
Schedule::command(...)/Schedule::job(...)entry; wire log destinations andrunInBackground()if needed. - Verify — Run
php artisan schedule:test(orschedule:list) and confirm timing, output path, and overlap behavior.
In routes/console.php (Laravel 11+)
use Illuminate\Support\Facades\Schedule;
Schedule::command('reports:generate')->dailyAt('06:00');
Schedule::command('telescope:prune --hours=48')->daily();
Schedule::command('queue:prune-batches --hours=48')->daily();
Schedule::job(new CleanupTemporaryFiles())->hourly();
Frequency helpers
| Method | Schedule |
|---|---|
->everyMinute() |
Every minute |
->everyFiveMinutes() |
Every 5 minutes |
->everyFifteenMinutes() |
Every 15 minutes |
->hourly() |
Every hour |
->hourlyAt(17) |
Every hour at :17 |
->daily() |
Daily at midnight |
->dailyAt('13:00') |
Daily at 1 PM |
->twiceDaily(1, 13) |
Daily at 1 AM and 1 PM |
->weekly() |
Weekly on Sunday at midnight |
->weeklyOn(1, '8:00') |
Weekly on Monday at 8 AM |
->monthly() |
Monthly on the 1st at midnight |
->monthlyOn(4, '15:00') |
Monthly on the 4th at 3 PM |
->quarterly() |
Quarterly |
->yearly() |
Yearly |
Cron expressions
Schedule::command('reports:generate')->cron('0 6 * * 1-5'); // Weekdays at 6 AM
Overlap prevention
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.
- 4d ago Changed · +2 lines 1d79689ad17c
- 9d ago First seen · 183 lines · 28 tokens per session scan A 094536681a33
laravel-scheduling is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,409 once invoked, about $0.0001 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
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
iblai-api-agent-support
Manage an ibl.ai agent's human-support tickets via the platform API — list and filter the tickets users raised with an agent (by agent, requester, status, session), read a ticket's conversation thread, reply as the support team, change ticket status, and close or delete tickets. Use when triaging or responding to…
strapi
Strapi headless CMS with REST and GraphQL. Use for content APIs.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.