agentmods.dev

tmux-mcp: Instructions file for Codex

AGENTS.md

tmux-mcp AGENTS.md is an instructions file for Codex, OpenCode from bnomei/tmux-mcp. It costs 665 tokens per session, scanned A, original, MIT.

Repository instructions for a Rust service that lets coding agents work with tmux, a terminal multiplexer for running and managing several shell sessions. They cover the source layout, tests, commands, security checks, and release packages.

In plain words
What is it for?
Use them when changing the Rust server or command-line tool, its tmux and SSH wrappers, security policies, tests, npm and Docker packages, or release scripts.
Why use it?
They give contributors a shared map of the project and make builds, tests, packaging, and tmux-related behavior more consistent.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is bnomei/tmux-mcp's own configuration. It tells Codex and OpenCode how to work on tmux-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tmux-mcp configures →

not rated 52repo +3 1mo ago A scan 665 tokens original MIT
View source ↗ bnomei/tmux-mcp crates.io
Reuse

Borrowing it

Nothing to install: this file belongs to bnomei/tmux-mcp. 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/bnomei/tmux-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/bnomei/tmux-mcp

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.

agentmods badge for tmux-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/bnomei/tmux-mcp/agents-md.svg)](https://agentmods.dev/instructions/bnomei/tmux-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/bnomei/tmux-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/bnomei/tmux-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 665 This file is loaded in full into every session.
When invoked 665 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00665 $0.00665
Opus 5 $0.00332 $0.00332
Sonnet 5 $0.00133 $0.00133
Haiku 4.5 $0.00067 $0.00067

Measured 8d ago against content hash 748f1eab3633, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

tmux-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 8d 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 · 39 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

  • src/ holds the Rust crate. Key files: main.rs (CLI entry), lib.rs (library exports), server.rs (MCP server), tmux.rs (tmux process wrapper), security.rs (policy checks/config schema), commands.rs, types.rs, errors.rs, and test_support.rs (tmux/ssh stubs for tests).
  • tests/ contains Rust tests: cli.rs for CLI behavior and integration.rs for tmux-backed workflows.
  • scripts/ holds release packaging helpers (build-release, package-release, resolve-version).
  • npm/tmux-mcp-rs/: npm wrapper package (@bnomei/tmux-mcp-rs) that downloads the matching GitHub Release binary at first run.
  • Dockerfile: multi-arch image that fetches musl Linux release assets and runs on Alpine with tmux.
  • packaging/README.md describes npm/Docker/Homebrew packaging surfaces.
  • docs/RELEASE.md is the release guide.
  • Build outputs live in target/ and dist/ (both generated).

Build, Test, and Development Commands

  • cargo build --release builds the tmux-mcp-rs binary in target/release/.
  • cargo test --lib runs unit tests without tmux.
  • cargo test --test cli runs CLI tests without tmux.
  • TMUX_MCP_INTEGRATION=1 cargo test --test integration runs tmux integration tests (requires tmux on PATH).
  • Release packaging: TARGET=... VERSION=... scripts/build-release.sh then scripts/package-release.sh.

Coding Style & Naming Conventions

  • Rust 2021 edition; prefer rustfmt defaults (cargo fmt) when formatting.
  • Use standard Rust naming: snake_case for functions/modules, CamelCase for types.
  • CLI flags use kebab-case (for example, --shell-type, --socket).
  • Tests should use clear test_* names and mirror the feature being exercised.

Testing Guidelines

  • Frameworks: Rust test harness plus rstest for fixtures; integration tests live in tests/integration.rs.
  • Integration tests create isolated tmux servers; keep them deterministic and ensure cleanup.
  • Prefer adding tests alongside new tool behavior or security checks.

Read the full file on GitHub · 39 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. 8d ago First seen · 39 lines · 665 tokens per session scan A 748f1eab3633

Subscribe to this mod's changes

tmux-mcp AGENTS.md is an instructions file published in the GitHub repository bnomei/tmux-mcp (52 stars, last pushed 1mo ago), licensed MIT. It adds 665 tokens to every session, about $0.0033 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.

agentclimcpmcp-serverprobe-and-refinetmux
Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens