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/anthonyposchen/agent-skills/omarchy-developmentnpx skills add AnthonyPoschen/agent-skills --skill omarchy-developmentgit clone --depth 1 https://github.com/AnthonyPoschen/agent-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/anthonyposchen/agent-skills/omarchy-development)<a href="https://agentmods.dev/skills/anthonyposchen/agent-skills/omarchy-development"><img src="https://agentmods.dev/badge/skills/anthonyposchen/agent-skills/omarchy-development.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.00111 | $0.01438 |
| Opus 5 | $0.00056 | $0.00719 |
| Sonnet 5 | $0.00022 | $0.00288 |
| Haiku 4.5 | $0.00011 | $0.00144 |
Grade B, and why
omarchy-development scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo systemctl enable --now libvirtd.service How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Omarchy Development
Develop Omarchy in a checkout and test it in a disposable guest. The host's installed Omarchy must stay on its packaged version: do not run omarchy dev link, restart the host shell, or reboot the host to test source changes.
Read source guidance first
In the Omarchy checkout, read AGENTS.md. Then read every linked task guide relevant to the change, especially:
agents/skills/shell-dev.mdfor QML/shell work.agents/skills/acceptance-tests.mdfor graphical acceptance tests.agents/skills/visual-verification.mdfor visible UI changes.
Run focused source tests before using the VM. For shell changes, this normally includes the affected test/shell.d/*-test.sh and qmllint on changed QML files.
Prepare the host once
Install the virtualization stack only with the user's authorization. Use sudo from an interactive terminal; when an agent cannot enter a password, use pkexec.
omarchy pkg add qemu-desktop qemu-full libvirt virt-manager dnsmasq edk2-ovmf swtpm
sudo systemctl enable --now libvirtd.service
sudo usermod -aG libvirt "$USER"
sudo virsh net-start default
sudo virsh net-autostart default
The user must log out and back in before Virtual Machine Manager can use the new libvirt group membership. Confirm KVM is available with test -r /dev/kvm.
Use the official omacom-io/omarchy-iso harness to make an installed base once. Keep the ISO outside /tmp and verify its published checksum. The harness's --install-only mode creates a reusable base.qcow2; never boot or write that base directly.
Create a GUI-managed disposable overlay
Use a separate source worktree per change and an overlay directory per VM. Store overlays under ~/VMs/omarchy-<feature>/, not /tmp.
VM_NAME=omarchy-<feature>
VM_DIR="$HOME/VMs/$VM_NAME"
BASE_DISK=/absolute/path/to/base.qcow2
BASE_VARS=/absolute/path/to/OVMF_VARS.4m.fd
mkdir -p "$VM_DIR"
qemu-img create -f qcow2 -b "$BASE_DISK" -F qcow2 "$VM_DIR/disk.qcow2"
cp "$BASE_VARS" "$VM_DIR/OVMF_VARS.4m.fd"
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 · 132 lines · 111 tokens per session scan B 8ff7912e13ac
omarchy-development is a skill published in the GitHub repository AnthonyPoschen/agent-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 111 tokens to every session and 1,438 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…