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/wavyrai/tmux-ide/agents-mdgit clone --depth 1 https://github.com/wavyrai/tmux-ideWrote 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/wavyrai/tmux-ide/agents-md)<a href="https://agentmods.dev/instructions/wavyrai/tmux-ide/agents-md"><img src="https://agentmods.dev/badge/instructions/wavyrai/tmux-ide/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.03051 | $0.03051 |
| Opus 5 | $0.01525 | $0.01525 |
| Sonnet 5 | $0.00610 | $0.00610 |
| Haiku 4.5 | $0.00305 | $0.00305 |
Grade A, and why
tmux-ide 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 5d 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tmux-ide
A visual, agent-aware IDE for ordinary tmux sessions. .tmux-ide/workspace.yml
is an optional declarative layout preset.
Quick Start
tmux-ide # Visual tmux app; configless by default
tmux-ide app [session] # Explicit app entry; optionally open a live session
tmux-ide init # Scaffold .tmux-ide/workspace.yml (auto-detects stack)
tmux-ide inspect # Show resolved config + live tmux state
tmux-ide stop # Kill session
tmux-ide attach # Reattach to running session
.tmux-ide/workspace.yml Format
version: 1
name: project-name # tmux session name
before: pnpm install # optional pre-launch hook
terminal:
theme: # optional color overrides
accent: colour75
border: colour238
bg: colour235
fg: colour248
rows:
- size: 70% # row height percentage
panes:
- title: Claude 1 # pane border label
command: claude # command to run (optional)
size: 50% # pane width percentage (optional)
dir: apps/web # per-pane working directory (optional)
focus: true # initial focus (optional)
env: # environment variables (optional)
PORT: 3000
- panes:
- title: Dev Server
command: pnpm dev
- title: Shell
The project file is optional: the app discovers and manages ordinary live tmux
sessions without one. Legacy ide.yml files are still supported through a compatibility adapter. Use
tmux-ide migrate --dry-run to preview conversion and tmux-ide migrate --write
to create .tmux-ide/workspace.yml.
WorkspaceConfigV1 can declare harnesses, agents, and missions data, but
mission runtime wiring is future work. Do not add legacy team, pane
role/task, sidebar, or orchestrator fields to .tmux-ide/workspace.yml.
Widget Pane Types
panes:
- title: Explorer
type: explorer # explorer | changes | preview | setup | config | sidebar
target: src/ # optional target path
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.
- 5d ago First seen · 337 lines · 3,051 tokens per session scan A ab93b37592f1
tmux-ide AGENTS.md is an instructions file published in the GitHub repository wavyrai/tmux-ide (543 stars, last pushed today), licensed MIT. It adds 3,051 tokens to every session, about $0.0153 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
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.
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.
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).
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.
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 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).