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/tmux-python/libtmux-mcp/agents-mdgit clone --depth 1 https://github.com/tmux-python/libtmux-mcpWhat 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.00862 | $0.00862 |
| Opus 5 | $0.00431 | $0.00431 |
| Sonnet 5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
libtmux-mcp 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 2d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
libtmux-mcp is a Model Context Protocol server that gives an AI agent programmatic control over tmux — sessions, windows, panes — built on libtmux.
Follow the conventions already in the tree, and keep a change scoped to what was asked for.
What is here
| Path | What it is |
|---|---|
src/libtmux_mcp/server.py |
FastMCP instance: construction, instructions, lifespan |
src/libtmux_mcp/middleware.py |
Toolset gating, response limiting, error mapping |
src/libtmux_mcp/_utils.py |
Server cache, object resolvers/serializers, handle_tool_errors |
src/libtmux_mcp/models.py |
Pydantic models for tool outputs |
src/libtmux_mcp/tools/ |
MCP tool implementations: one module per tmux object, plus batch/buffer/hook/wait_for |
src/libtmux_mcp/resources/ |
tmux:// URI resources for browsing the hierarchy |
src/libtmux_mcp/prompts/ |
MCP prompt templates |
scripts/mcp_swap.py |
Dev script: point agent CLI configs at a local checkout |
tests/ |
pytest suite; tests/docs/ covers doc-widget and topic contracts |
docs/ |
Sphinx source; docs/tools/ mirrors tools/, one page per tool |
CHANGES |
Changelog, included into the built docs/history.md page |
conftest.py |
Root doctest fixtures — see .github/WRITING.md |
Which policy applies
- Documentation, user-facing text,
CHANGES, release notes, commit messages, docstrings, and source comments: .github/WRITING.md - Environment, the gates, tests, documentation builds, releases, and pull requests: .github/CONTRIBUTING.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.
- 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.
- Add a test for every user-visible behaviour change, and a
CHANGESentry for every change to a tool, resource, prompt, or configuration variable. - 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.
- 2d ago First seen · 69 lines · 862 tokens per session scan A 21784c5fd269
libtmux-mcp AGENTS.md is an instructions file published in the GitHub repository tmux-python/libtmux-mcp (12 stars, last pushed 2d ago), licensed MIT. It adds 862 tokens to every session, about $0.0043 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-30.
Other instructions, from other repositories
obsidian-mind CLAUDE.md
Claude Code instructions for breferrari/obsidian-mind, covering obsidian mind, skills & capabilities, custom slash commands, vault structure and obsidian cli.
obsidian-mind AGENTS.md
AGENTS.md instructions for breferrari/obsidian-mind, covering obsidian mind, hooks, commands, memory and reaching this vault from another repo.
parallel-code CLAUDE.md
Instructions for johannesjo/parallel-code, covering parallel code, stack, commands, project structure and conventions.
neo4j-skills AGENTS.md
Instructions for neo4j-contrib/neo4j-skills, covering writing skills for this repository, language style — write for agents, not humans, six design principles, skill.md spec (agentskills.io) and frontmatter.
ox AGENTS.md
Instructions for sageox/ox, covering human attention is the scarcest resource, what is ox?, quick start, terminology and required reviews.
cligent AGENTS.md
Instructions for sublang-ai/cligent, covering agents and specs (source of truth).