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 agentmods add skills/fusengine/agents/laravel-queuesnpx skills add fusengine/agents --skill laravel-queuesgit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/laravel-queues)<a href="https://agentmods.dev/skills/fusengine/agents/laravel-queues"><img src="https://agentmods.dev/badge/skills/fusengine/agents/laravel-queues.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.01596 |
| Opus 5 | $0.00016 | $0.00798 |
| Sonnet 5 | $0.00006 | $0.00319 |
| Haiku 4.5 | $0.00003 | $0.00160 |
Grade A, and why
laravel-queues 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 today.
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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel Queues (L13 — Attributes-first)
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Audit job classes, connections, queue routes
- fuse-ai-pilot:research-expert - Verify L13 Queue + Queue::route() via Context7
- mcp__context7__query-docs - Check queue attribute patterns
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
Laravel 13 introduces PHP Attributes on Queueables (Jobs, Listeners, Notifications, Mailables, Broadcast Events) as the primary configuration mechanism. Centralised routing is configured via Queue::route() in AppServiceProvider::boot().
| Attribute (L13 MAIN) | Legacy property |
|---|---|
#[Connection('redis')] · #[Queue('podcasts')] |
public $connection · public $queue |
#[Tries(5)] · #[Timeout(120)] · #[MaxExceptions(3)] |
public int $tries / $timeout / $maxExceptions |
#[Backoff([10, 30, 60])] · #[FailOnTimeout] |
public $backoff · public bool $failOnTimeout |
#[UniqueFor(3600)] · #[AfterCommit] · #[DeleteWhenMissingModels] |
public $uniqueFor / $afterCommit / $deleteWhenMissingModels |
Applies to Jobs, Listeners, Notifications, Mailables, and Broadcast Events.
Critical Rules
- Declare queue metadata with Attributes -
#[Queue],#[Tries],#[Backoff] - Centralise routing with
Queue::route()inAppServiceProvider::boot() - Implement
failed(Throwable $e)for every production job - Use
#[AfterCommit]when dispatching inside DB transactions - Monitor Redis queues with Horizon in production
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/batching.md 2.1 KB
- references/chaining.md 2.4 KB
- references/dispatching.md 2.0 KB
- references/failed-jobs.md 1.8 KB
- references/horizon.md 2.0 KB
- references/jobs.md 2.7 KB
- references/legacy-properties.md 4.0 KB
- references/middleware.md 1.8 KB
- references/templates/BatchJob.php.md 5.1 KB
- references/templates/ChainedJobs.php.md 6.0 KB
- references/templates/JobMiddleware.php.md 6.1 KB
- references/templates/JobTest.php.md 7.5 KB
- references/templates/QueueableJob.php.md 3.6 KB
- references/testing.md 2.0 KB
- references/troubleshooting.md 2.0 KB
- references/workers.md 1.9 KB
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.
- today Changed 214028dc4919
- yesterday First seen · 159 lines · 32 tokens per session scan A 6389b71430a0
laravel-queues is a skill published in the GitHub repository fusengine/agents (25 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,596 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
radin-record
Log feedback, bugs, follow-ups, or ideas raised mid-session as structured backlog entries, so they survive past the conversation. Use for /radin-record, "log this to the backlog", "add as follow-up/bug/idea", "record what we just found", "note this for later", "add findings to backlog". Triggers even on vague asks…
radin-doctor
Check that radin's own install under /.claude is complete and its optional companion tools are reachable. Use for /radin-doctor, "check my radin install", "is radin installed correctly", "radin doctor", "verify radin install".
designing-interfaces
Creates a design system for software with a UI. Use when a project has a user interface and architecture is confirmed — whether creating from scratch or extracting patterns from existing code.
managing-product
Extracts product requirements and produces a PRD. Use when a user wants to build software and needs to define what to build before architecture or implementation, when scoping an MVP, or when translating a vague idea into a buildable specification.
orchestrating-software-dev
Runs software development projects from idea to completion. Use when starting a software project, adding a feature, fixing a bug, or resuming an in-progress build.
collecting-sources
Collects research sources with quality evaluation. Use when gathering or finding sources, building a source library, searching for academic papers, or performing RADAR assessment.