Borrowing it
Nothing to install: this file belongs to libtmux/libtmux-go. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/libtmux/libtmux-go/master/AGENTS.mdgit clone --depth 1 https://github.com/libtmux/libtmux-goWrote 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/libtmux/libtmux-go/agents-md)<a href="https://agentmods.dev/instructions/libtmux/libtmux-go/agents-md"><img src="https://agentmods.dev/badge/instructions/libtmux/libtmux-go/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.
<a href="https://agentmods.dev/instructions/libtmux/libtmux-go/agents-md"><img src="https://agentmods.dev/badge/instructions/libtmux/libtmux-go/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00768 | $0.00768 |
| Opus 5.5 | $0.00307 | $0.00307 |
| Sonnet 5.5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
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 1mo 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 — 65 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
Six 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 |
internal/tools/ |
developer tool | Rewires MCP clients without shipping in a release module |
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
- Documentation, user-facing text,
CHANGELOG.md, release notes, commit messages, doc comments, and source comments: .github/WRITING.md - Building, testing, linting, the Go floor, the tmux matrix, and pull requests: .github/CONTRIBUTING.md
- Anything under
mcp/: mcp/AGENTS.md - Reporting or assessing a vulnerability: SECURITY.md
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.
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.
- 1mo ago Changed · +1 lines · +22 tokens per session 2331f839c695
- 2mo ago First seen · 64 lines · 746 tokens per session scan A a590d61bae48
libtmux-go AGENTS.md is an instructions file published in the GitHub repository libtmux/libtmux-go (0 stars, last pushed today), licensed MIT. It adds 768 tokens to every session, about $0.0031 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-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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.