libtmux-go AGENTS.md

Repository instructions for libtmux/libtmux-go, a Go library for controlling the terminal multiplexer tmux. They explain the project structure, applicable policies, and coding conventions.

In plain words
What is it for?
Use them when changing libtmux/libtmux-go, especially when choosing the right module, following local conventions, or checking repository-specific policies.
Why use it?
They prevent agents from applying Python project habits to Go code or making changes outside the requested scope.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/libtmux/libtmux-go/agents-md
Clone the repo
git clone --depth 1 https://github.com/libtmux/libtmux-go

Made for: Codex, OpenCode.

Per session 746 This file is loaded in full into every session.
When invoked 746 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00746 $0.00746
Opus 5 $0.00373 $0.00373
Sonnet 5 $0.00149 $0.00149
Haiku 4.5 $0.00075 $0.00075

Measured yesterday against content hash a590d61bae48, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

libtmux-go 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.

AGENTS.md · 64 lines

How it starts

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

AGENTS.md

Rules for this repository: libtmux for Go, a port of the Python library of the same name. Nothing here is Python — a convention you recognise from that project (uv, ruff, mypy, pytest, doctests, NumPy docstrings) does not apply unless a file here says so.

Follow the conventions already in the tree, and keep a change scoped to what was asked for.

What is here

Five Go modules, each with its own go.mod:

Path Module What it is
. the tmux module Server, sessions, windows, panes, options, hooks, formats, filters, snapshots, connections, and plans. Zero runtime dependencies.
workspace/ consumer Loads tmuxp-style YAML workspaces and builds them
mcp/ consumer Serves one tmux server to Model Context Protocol clients
examples/ consumer Compiles the examples quoted in generated documentation
benchmarks/ tool Prints what each way of reaching tmux costs

Inside the tmux module, tmuxq holds model-free generics, tmuxtest gives tests a real tmux server that cleans itself up, and internal/ holds the subprocess transport, the checked-in generators, and internal/integration. examples/ is a module of its own.

Which policy applies

Each of those is the single home for its subject. Where a rule seems to be stated twice, the file listed above is the one that governs.

Change discipline

  • Make the smallest coherent change that solves the verified problem; keep unrelated cleanup out of it.
  • Reuse an existing file, helper, API, or test before adding a new one.
  • Keep new APIs unexported until a caller outside the package needs them.
  • Add a file only for a durable boundary — a distinct responsibility, independent reuse, or splitting an oversized module — not for a single-use helper or a one-line re-export.
  • A passing gate is evidence only once it has been shown capable of failing. Pair a new test with a deliberate break that proves it bites.

Read the full file on GitHub · 64 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.

  1. yesterday First seen · 64 lines · 746 tokens per session scan A a590d61bae48

Subscribe to this mod's changes

libtmux-go AGENTS.md is an instructions file published in the GitHub repository libtmux/libtmux-go (0 stars, last pushed 2d ago), licensed MIT. It adds 746 tokens to every session, about $0.0037 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.