What is omarchy-pods AGENTS.md?

Instructions for coding agents working on omarchy-pods, a project built with CMake and Ninja and tested with CTest. They explain the required build process, test limitations, change-review expectations, and assumptions to report.

Use them when building, testing, reviewing, or changing the daemon, especially its CMake configuration, Qt tests, source timestamps, or agent-authored changes.

They highlight repository-specific mistakes, such as linking unsupported libraries into tests or trusting stale build files after copying sources.

How thisisgm/omarchy-pods configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to thisisgm/omarchy-pods. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/thisisgm/omarchy-pods/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/thisisgm/omarchy-pods

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/thisisgm/omarchy-pods/agents-md/github.svg)](https://agentmods.dev/instructions/thisisgm/omarchy-pods/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/thisisgm/omarchy-pods/agents-md"><img src="https://agentmods.dev/badge/instructions/thisisgm/omarchy-pods/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/thisisgm/omarchy-pods/agents-md"><img src="https://agentmods.dev/badge/instructions/thisisgm/omarchy-pods/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 972 This file is loaded in full into every session.

When invoked 972 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00972	$0.00972
Opus 5.5	$0.00389	$0.00389
Sonnet 5.5	$0.00194	$0.00194
Haiku 4.5	$0.00097	$0.00097

Measured 2mo ago against content hash 89929b59e835, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

omarchy-pods 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 2mo 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.

AGENTS.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Read CONTRIBUTING.md first. It is the contract for everybody, and nothing here replaces it. This file adds the handful of things coding agents get wrong in this repo specifically.

Agent-authored PRs are welcome and several are already merged. They are held to the same bar as any other, which in practice means the review will ask for evidence rather than for confidence.

The build, once

cd daemon
cmake -B build -G Ninja
cmake --build build
ctest --test-dir build

Two traps that have cost real time here:

daemon/tests/CMakeLists.txt links only Qt6::Test and Qt6::Core, so a test that reaches BlueZ, PulseAudio or Qt6::Widgets cannot exist. Do not "fix" that by widening the link line. Move the logic somewhere testable instead.
If you build on one machine and run on another, do not trust an incremental build after copying sources with preserved timestamps. rsync -a can leave a source older than the object built from it, and the compiler will skip it. This produces a green run of code you never compiled.

What gets a change sent back

Unrequested generality. A parameter with one caller, a mode nothing runs, a guard for a state this platform cannot reach. Delete it and say what the platform actually does.
Comment paragraphs. One line, stating the constraint. Two or three only for a real timing or race constraint.
A green suite offered as proof. Run the failing case first and show it red. If you cannot drive the defect, say that instead of implying you did.
Invented abbreviations and em dashes. Both are in CONTRIBUTING.md and both are checked.
AI attribution. No Co-Authored-By for a tool, no "Generated with" line, anywhere: commits, PR bodies, comments.

The output codec is not negotiable

The daemon selects the highest-bitrate playback profile the card offers, SBC-XQ at 453 kbps ahead of SBC at 328 and AAC at 256, and re-applies it on every activation because PipeWire's priority order puts AAC first. A change that lowers the selected bitrate is a defect here even when it reads as a simplification, and a guard that quietly skips the selection is the same defect in a different costume. One of those has already shipped and been reverted.

Read the full file on GitHub · 84 lines

Changes

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.

2mo ago First seen · 84 lines · 972 tokens per session scan A 89929b59e835

Subscribe to this mod's changes

omarchy-pods AGENTS.md is an instructions file published in the GitHub repository thisisgm/omarchy-pods (246 stars, last pushed 2mo ago), licensed MIT. It adds 972 tokens to every session, about $0.0039 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-08-30.

omarchy-pods AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
omarchy-pods AGENTS.mdthisisgm/omarchy-pods	Instructions file	246	2mo ago	MIT	A	972	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	275k	2d ago	MIT	A	4,313	Codex, OpenCode

omarchy-pods: Instructions file for Codex