Omarchy is a Linux distribution with a predefined desktop environment, tools, settings, and workflows. Developers and other Linux users use it as their operating system, including for terminal work, programming, gaming, and everyday applications. The catalogue entries provide instructions and skills for working with Omarchy.
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 omacom/omarchy --skill diagnose-crashgit clone --depth 1 https://github.com/omacom/omarchyWrote 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/omacom/omarchy/diagnose-crash)<a href="https://agentmods.dev/skills/omacom/omarchy/diagnose-crash"><img src="https://agentmods.dev/badge/skills/omacom/omarchy/diagnose-crash/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/omacom/omarchy/diagnose-crash"><img src="https://agentmods.dev/badge/skills/omacom/omarchy/diagnose-crash.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- 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.00116 | $0.01339 |
| Opus 5 | $0.00058 | $0.00669 |
| Sonnet 5 | $0.00023 | $0.00268 |
| Haiku 4.5 | $0.00012 | $0.00134 |
Grade A, and why
diagnose-crash 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 8d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnosing a Crash
Work from evidence. The goal is an honest account of what happened, not a plausible-sounding story.
Establish the facts
coredumpctl info <pid> is the starting point. Beyond the backtrace, note the
command line the process was started with — it usually reveals what the
program was working on when it died, which is often the whole answer.
coredumpctl list shows whether this crash is a one-off or a pattern. Repeated
crashes of the same program, or several programs dying together, point somewhere
different than a single failure does.
Rule out the boring causes first
Check resource exhaustion before blaming the program: free -h, and the journal
for OOM kills. A process killed by the OOM killer is not a bug in that process.
Correlate against the timeline
The crash timestamp is the most underused piece of evidence. Compare it against:
- Filesystem mtimes. A directory or file whose mtime lands on the same second as the crash strongly suggests what triggered it.
- The journal around that moment, for related warnings from the same or neighbouring processes.
- Recent package updates. A crash that starts right after an update points at the update.
Read the whole core, not just frame 0
Thread stacks other than the crashing one show what work was in flight — thumbnailers, image loaders, IPC readers, GPU queues. That context often explains the trigger even when the crashing frame itself cannot be symbolized.
Note any third-party code in the address space: file-manager or browser extensions, plugins, out-of-tree drivers. In-process third-party code is a common crash source and worth flagging — but do not pin blame on it without evidence that it is actually implicated.
Symbolize when you can
This is Arch, which runs a public debuginfod server:
core=$(mktemp -t crash-XXXXXX.core)
trap 'rm -f "$core"' EXIT
coredumpctl dump <pid> --output="$core"
DEBUGINFOD_URLS="https://debuginfod.archlinux.org" \
gdb -q <executable> "$core" \
-batch -ex 'set debuginfod enabled on' -ex 'bt'
What ships with it
1 file 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.
- 8d ago First seen · 129 lines · 116 tokens per session scan A 0762bb8c913a
diagnose-crash is a skill published in the GitHub repository omacom/omarchy (39,036 stars, last pushed today), licensed MIT. It adds 116 tokens to every session and 1,339 once invoked, about $0.0006 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-31.
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.