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/pranav7/domux/agents-mdgit clone --depth 1 https://github.com/pranav7/domuxWrote 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/instructions/pranav7/domux/agents-md)<a href="https://agentmods.dev/instructions/pranav7/domux/agents-md"><img src="https://agentmods.dev/badge/instructions/pranav7/domux/agents-md.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.00515 | $0.00515 |
| Opus 5 | $0.00258 | $0.00258 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
domux 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 3d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
domux is a small Go CLI/TUI in one root package. Core entrypoints and command
handlers live in main.go, commands.go, and state_commands.go. Session,
store, resolver, install, picker, and TUI behavior are split into matching
*.go files at the repo root. Tests live beside code as *_test.go. Runtime
state is external: TODO files under ~/.local/share/domux/, generated
integrations under ~/.config/domux/. The built domux binary and dist/ are
ignored.
Build, Test, and Development Commands
go test ./...runs all unit tests.go build ./...checks every package builds.go run .starts the TODO TUI for the current domux context.go run . sessionsopens the session picker.go run . install tmuxpreviews generated tmux integration.go run . install tmux --applywrites integration files; review preview first.gofmt -w *.goformats root Go files before commit.
Coding Style & Naming Conventions
Use standard Go style: tabs from gofmt, short package-local names, simple data
structures, and explicit error returns. Keep this repo self-contained and avoid
unneeded abstraction. Test names use TestBehaviorCondition, matching existing
examples like TestPickerEscapeQuitsAfterStartup.
Testing Guidelines
Use Go's built-in testing package. Add focused tests beside the file under
change, especially for session state, install output, picker behavior, and store
parsing. Prefer table tests only when cases share the same setup. Run
go test ./... before handing off.
Commit & Pull Request Guidelines
Recent commits use concise imperative subjects, for example Clear stale PR state with session state. Keep subjects short, no trailing period. Do not commit
directly to restricted branches (main, master, workspace-*) unless
explicitly told.
PRs should include a short problem/solution summary, tests run, and screenshots or terminal output for visible TUI or integration changes. Link issues when relevant.
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.
- 3d ago First seen · 52 lines · 515 tokens per session scan A 03ff23a77875
domux AGENTS.md is an instructions file published in the GitHub repository pranav7/domux (5 stars, last pushed 5d ago), licensed MIT. It adds 515 tokens to every session, about $0.0026 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
agent-of-empires AGENTS.md
AGENTS.md instructions for agent-of-empires/agent-of-empires, covering repository guidelines, where to look, commands, code rules and tests.
terminal-browser AGENTS.md
AGENTS.md instructions for zenbu-labs/terminal-browser, a project described as: A browser inside your terminal.
wispterm AGENTS.md
Instructions for xuzhougeng/wispterm, covering agents.md, architecture, ui presentation styles, cohesion and coupling and integration layer vs feature domains.
vibetunnel GEMINI.md
Instructions for amantus-ai/vibetunnel: When I am operating within this project, I must adhere to the following instructions.
terminal AGENTS.md
Instructions for browser-use/terminal, covering agent notes, rust rewrite verification loop and terminal ui testing standard.
hex1b AGENTS.md
Instructions for mitchdenny/hex1b, covering ai coding agent guidelines for hex1b, 🛠️ available skills, 📋 project overview, key technologies and repository layout.