configuring-horizon

A set of instructions for installing and configuring Laravel Horizon, a dashboard and process manager for Laravel's queued background jobs. It covers workers, queues, scaling, monitoring, notifications, tags, and metrics.

In plain words
What is it for?
Use it to install Horizon, configure supervisors and queue balancing, set up alerts and tags, manage metrics, and control dashboard access.
Why use it?
It helps configure workers to process the right queues and makes problems such as long waits, missing metrics, or incorrect dashboard access easier to address.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/ohnotnow/devnotes/configuring-horizon
Any agent
npx skills add ohnotnow/devnotes --skill configuring-horizon
Clone the repo
git clone --depth 1 https://github.com/ohnotnow/devnotes

Made for: Claude Code, Codex.

Per session 137 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 768 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00137 $0.00768
Opus 5 $0.00068 $0.00384
Sonnet 5 $0.00027 $0.00154
Haiku 4.5 $0.00014 $0.00077

Measured yesterday against content hash 9e8c18906c4b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

configuring-horizon 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 yesterday.

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.

Origin

This is a copy

100% identical to configuring-horizon — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/configuring-horizon/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Horizon Configuration

Documentation

Use search-docs for detailed Horizon patterns and documentation covering configuration, supervisors, balancing, dashboard authorization, tags, notifications, metrics, and deployment.

For deeper guidance on specific topics, read the relevant reference file before implementing:

  • references/supervisors.md covers supervisor blocks, balancing strategies, multi-queue setups, and auto-scaling
  • references/notifications.md covers LongWaitDetected alerts, notification routing, and the waits config
  • references/tags.md covers job tagging, dashboard filtering, and silencing noisy jobs
  • references/metrics.md covers the blank metrics dashboard, snapshot scheduling, and retention config

Basic Usage

Installation

php artisan horizon:install

Supervisor Configuration

Define supervisors in config/horizon.php. The environments array merges into defaults and does not replace the whole supervisor block:

'defaults' => [
    'supervisor-1' => [
        'connection' => 'redis',
        'queue' => ['default'],
        'balance' => 'auto',
        'minProcesses' => 1,
        'maxProcesses' => 10,
        'tries' => 3,
    ],
],

'environments' => [
    'production' => [
        'supervisor-1' => ['maxProcesses' => 20, 'balanceCooldown' => 3],
    ],
    'local' => [
        'supervisor-1' => ['maxProcesses' => 2],
    ],
],

Dashboard Authorization

Restrict access in App\Providers\HorizonServiceProvider:

protected function gate(): void
{
    Gate::define('viewHorizon', function (User $user) {
        return $user->is_admin;
    });
}

Verification

  1. Run php artisan horizon and visit /horizon
  2. Confirm dashboard access is restricted as expected
  3. Check that metrics populate after scheduling horizon:snapshot

Common Pitfalls

  • Horizon only works with the Redis queue driver. Other drivers such as database and SQS are not supported.
  • Redis Cluster is not supported. Horizon requires a standalone Redis connection.
  • Always check config/horizon.php before making changes to understand the current supervisor and environment configuration.
  • The environments array overrides only the keys you specify. It merges into defaults and does not replace it.
  • The timeout chain must be ordered: job timeout less than supervisor timeout less than retry_after. The wrong order can cause jobs to be retried before Horizon finishes timing them out.
  • The metrics dashboard stays blank until horizon:snapshot is scheduled. Running php artisan horizon alone does not populate metrics.
  • Always use search-docs for the latest Horizon documentation rather than relying on this skill alone.

Read the full file on GitHub · 86 lines

Files

What ships with it

4 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.

Changes

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.

  1. yesterday First seen · 86 lines · 137 tokens per session scan A 9e8c18906c4b

Subscribe to this mod's changes

configuring-horizon is a skill published in the GitHub repository ohnotnow/devnotes (0 stars, last pushed yesterday), licensed MIT. It adds 137 tokens to every session and 768 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to configuring-horizon, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens