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 instructions/omacom/omarchy/agents-mdgit clone --depth 1 https://github.com/omacom/omarchyWhat 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.01914 | $0.01914 |
| Opus 5 | $0.00957 | $0.00957 |
| Sonnet 5 | $0.00383 | $0.00383 |
| Haiku 4.5 | $0.00191 | $0.00191 |
Grade A, and why
omarchy AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Guides
Deeper instructions for specific kinds of work live in agents/skills/. Read the
matching guide before starting:
agents/skills/command-metadata.md- adding or changing commands inbin/agents/skills/install-scripts.md- working underinstall/or on system/user setup commandsagents/skills/shell-dev.md- editing the Quickshell desktop undershell/agents/skills/icon-font.md- adding branded glyphs todefault/fonts/omarchy/omarchy.ttfagents/skills/acceptance-tests.md- writing or running graphical acceptance tests undertest/acceptance.d/agents/skills/visual-verification.md- verifying any change with a visual effect in the running UIagents/skills/migrations.md- creating or changing migrations undermigrations/
Documentation Layout
Three documentation trees, split by genre and audience:
agents/skills/- task procedure ("do this when doing X"), for anyone working on the codebasedocs/- reference on how the system is shaped (file layout, update pipeline, theming, shell architecture), for anyone working on the codebase; skills link here for depthmanual/- end-user documentation for using Omarchy, published; never codebase internals
Style
- In markdown documents (
plans/,docs/,manual/), write full lines — no hard wrapping at 80 columns; break only at structural boundaries like headings and list items - Two spaces for indentation, no tabs
- Use bash 5 conditionals: use
[[ ]]for string/file tests and(( ))for numeric tests - In
[[ ]], don't quote variables, but do quote string literals when comparing values (e.g.,[[ $branch == "dev" ]]) - Prefer
(( ))over numeric operators inside[[ ]](e.g.,(( count < 50 )), not[[ $count -lt 50 ]]) - Prefer a full
if/elseconditional for simple two-path control flow; don't rely onexecorexitin one branch to make following statements unreachable - For strings/paths with spaces, quote them instead of escaping spaces with
\(e.g.,"$APP_DIR/Disk Usage.desktop", not$APP_DIR/Disk\ Usage.desktop) - Shebangs must use
#!/bin/bashconsistently (never#!/usr/bin/env bash) - Scripts under
install/andmigrations/may be sourced and intentionally omit shebangs
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.
- yesterday First seen · 134 lines · 1,914 tokens per session scan A 1afac6a1c253
omarchy AGENTS.md is an instructions file published in the GitHub repository omacom/omarchy (35,979 stars, last pushed yesterday), licensed MIT. It adds 1,914 tokens to every session, about $0.0096 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.