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 Smirnov-Labs/claude-skills --skill hyprland-luagit clone --depth 1 https://github.com/Smirnov-Labs/claude-skillsWrote 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/smirnov-labs/claude-skills/hyprland-lua)<a href="https://agentmods.dev/skills/smirnov-labs/claude-skills/hyprland-lua"><img src="https://agentmods.dev/badge/skills/smirnov-labs/claude-skills/hyprland-lua/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/smirnov-labs/claude-skills/hyprland-lua"><img src="https://agentmods.dev/badge/skills/smirnov-labs/claude-skills/hyprland-lua.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00174 | $0.02598 |
| Opus 5.5 | $0.00070 | $0.01039 |
| Sonnet 5.5 | $0.00035 | $0.00520 |
| Haiku 4.5 | $0.00017 | $0.00260 |
Grade A, and why
hyprland-lua 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 5d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Controlling a Lua-configured Hyprland
Overview
Some Hyprland setups are configured in Lua (~/.config/hypr/hyprland.lua) instead of hyprland.conf — native since Hyprland 0.55 (embedded Lua 5.4; the compositor loads hyprland.lua in place of hyprland.conf when it exists — not a plugin). On these the whole IPC surface is parsed as Lua — classic hyprctl dispatch <name> / hyprctl keyword are DEAD and error. All runtime control goes through hyprctl eval '<lua>' wrapping hl.dispatch(hl.dsp.X(...)).
Core principle: when a dispatch keeps hitting the wrong or default target, suspect the argument form (string vs table) before blaming keybinds, focus, races, or "another agent."
When this applies
hyprctl dispatch workspace 3→')' expected near '3'(any Lua parse error)hyprctl keyword …→ "keyword can't work with non-legacy parsers. Use eval."- A scratchpad/special workspace won't hide, or an empty
special:specialkeeps appearing - Focus dispatches land on the wrong window/monitor (
input:follow_mouse=1) - You need to script show/hide/move/focus at runtime, or inspect live state
Detect via: ~/.config/hypr/hyprland.lua exists / no hyprland.conf, or a failing hyprctl dispatch.
Also in this skill (load on demand)
| File | For |
|---|---|
launcher.md |
Building a Wayland-native switcher/launcher (fuzzel over rofi), the two focus-landing bugs, workspace rename/move |
quickshell.md |
Hyprland ↔ Quickshell/QML integration — driving Hyprland from QML, the special-workspace badge + activespecial refresh (bar internals & rendering gotchas live in the separate quickshell-bar skill) |
Runtime dispatch — the wrapper
hyprctl eval 'hl.dispatch(hl.dsp.<path>(<args>))'
evalprintsokon success (return values swallowed) but surfaces Lua errors — use that to enumerate an unknown dispatcher table:hyprctl eval 'local s="" for k in pairs(hl.dsp.workspace) do s=s..k.."," end error(s)'hyprctl reloadre-executes the Lua from disk. Safe if autostart is gated behindhl.on("hyprland.start", …)(reload won't re-run those execs → no duplicate apps).- Queries are NOT Lua —
hyprctl clients -j,monitors -j,workspaces -j,cursorposwork normally. Drive everything from these +jq.
What ships with it
2 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.
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.
- 5d ago First seen · 127 lines · 174 tokens per session scan A 4d23dfa79b3f
hyprland-lua is a skill published in the GitHub repository Smirnov-Labs/claude-skills (6 stars, last pushed 2d ago), licensed MIT. It adds 174 tokens to every session and 2,598 once invoked, about $0.0007 per session on Opus 5.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-10-17.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…