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 IgorWarzocha/howaboua-pi-stuff --skill omarchy-helpgit clone --depth 1 https://github.com/IgorWarzocha/howaboua-pi-stuffWrote 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/igorwarzocha/howaboua-pi-stuff/omarchy-help)<a href="https://agentmods.dev/skills/igorwarzocha/howaboua-pi-stuff/omarchy-help"><img src="https://agentmods.dev/badge/skills/igorwarzocha/howaboua-pi-stuff/omarchy-help.svg" alt="Measured on agentmods" 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.00021 | $0.00772 |
| Opus 5 | $0.00010 | $0.00386 |
| Sonnet 5 | $0.00004 | $0.00154 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
omarchy-help 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.
What it actually says
- Identify the requested outcome and affected layer. Inspect only the relevant config, process, device, service, or log.
- Read the matching reference before acting:
- Hyprland, Quickshell, themes, defaults, bindings, input, displays, or local automation:
references/personalization.md - Update, refresh, reinstall, packages, snapshots, broad diagnostics, or staged recovery:
references/system-maintenance.md - User config lost or reset after an update:
references/config-recovery.md - Bluetooth adapter present but discovery broken:
references/bluetooth-fix.md - Process crash, core dump, or Omarchy crash notification:
references/crash-diagnosis.md - Freeze, heat, or stalled application:
references/runtime-triage.md - Blank or locked physical display while connected remotely:
references/remote-unlock.md
- Hyprland, Quickshell, themes, defaults, bindings, input, displays, or local automation:
- Resolve symlinks, generated files, and sourced config before editing. Treat
/usr/share/omarchy/and a compatibility link resolving there as read-only. Put durable customization in user-owned config. Inspect generated active state under~/.local/state/omarchy/current/and other remembered state under~/.local/state/omarchy/, but do not mistake either for editable source. - Discover current device names, services, applications, routes, and command behavior from the machine. Use
omarchy commands --jsonfor the current route surface and prefer a routedomarchy <group> <command>when it owns the task. Read an implementation before running a command with unclear replacement, removal, reset, upload, or system effects. - Treat the graphical session as an environment boundary. Before using
hyprctlfrom SSH or a TTY, identify the active Wayland session and import its current UWSM user-manager environment. A missing compositor socket from a remote shell does not prove Hyprland is down. - Choose the smallest durable action. Do not turn a focused change into a health audit, update, reset, or reinstall.
- Routine user-config edits and scoped component reloads are part of the requested work. Confirm an unrequested config refresh, reinstall, package removal, snapshot restore, channel change, boot, security, or storage change, logout, reboot, or shutdown. Do not ask again when the user requested that exact action and its scope is clear.
- Preserve unrelated config. Do not create backup clutter for small edits. Preserve rollback before broad replacement only when the command does not already do so.
- Validate the affected component and runtime behavior:
- Hyprland Lua: run
hyprctl reloadandhyprctl configerrors. - Shell JSON, menu JSONC, or user plugin: confirm
omarchy-shell shell ping. Runomarchy plugin validate <folder>for a plugin package. hyprsunset.conf: runomarchy restart hyprsunset.- Other components: use their native validation, then reload or restart only when needed.
- Hyprland Lua: run
- For intermittent failures, inspect the relevant current process state and journal before changing more config.
- Report the durable source changed, any reload or restart, and the observed result or exact blocker. Mention disruption, reboot requirements, generated backups, or manual follow-up only when applicable.
Do not capture the user's active desktop unless they requested the capture or approved the interruption. Prefer config, IPC, process, and runtime evidence.
Never upload diagnostics, logs, screenshots, recordings, or core dumps without explicit authorization.
What ships with it
7 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.
- 4d ago Changed · +18 lines · +2 tokens per session 63f935f1d8c3
- 8d ago First seen · 15 lines · 19 tokens per session scan A cc1225fcfe39
omarchy-help is a skill published in the GitHub repository IgorWarzocha/howaboua-pi-stuff (352 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 772 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-08-30.
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.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.