Borrowing it
Nothing to install: this file belongs to PiMPStudios/claude-tmux-bridge. 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/PiMPStudios/claude-tmux-bridge/main/CLAUDE.mdgit clone --depth 1 https://github.com/PiMPStudios/claude-tmux-bridgeWrote 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/pimpstudios/claude-tmux-bridge/claude-md)<a href="https://agentmods.dev/instructions/pimpstudios/claude-tmux-bridge/claude-md"><img src="https://agentmods.dev/badge/instructions/pimpstudios/claude-tmux-bridge/claude-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.1 | $0.01006 | $0.01006 |
| Opus 5 | $0.00503 | $0.00503 |
| Sonnet 5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
claude-tmux-bridge CLAUDE.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 7d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code MCP — tmux Bridge
What This Is
This is an MCP server that connects Claude Desktop to an interactive Claude Code session running in a named tmux pane. It delivers prompts from Desktop to Code and returns the response — maintaining full conversation history and tool access between calls.
How to Use This Tool (for Claude Desktop)
This server exposes one tool: claude_code.
When to use it
Use claude_code whenever the user wants Claude Code to execute a task — writing code, editing files, running commands, working with git, or using any tools Claude Code has access to (MCP tools, bash, file system, etc.).
Required parameters
prompt— the full task description to send to Claude CodeworkFolder— absolute path to the user's project directory (determines which tmux session to target)
Optional parameters
timeout— max seconds to wait for a response (default: 300)clearContext— send/clearbefore the prompt; wipes conversation history entirely. Fast (< 1s).compact— send/compactbefore the prompt; summarises history via the Claude API, keeping key context while freeing space. Slower (30–60s). Takes precedence overclearContextif both are set.
When to use clearContext
Use clearContext: true when:
- Starting a completely new feature, system, or unrelated task
- Beginning a fresh work session on a project you've worked on before
- Claude Code warns that the context window is getting large
- The previous task is fully done and the next task has no dependency on it
When to use compact
Use compact: true when:
- Context is growing large but the conversation history is still relevant
- You're mid-task and want to keep continuity without hitting context limits
- Claude Code's responses are getting slower or less accurate due to context size
How to write a good prompt for Claude Code
- Be explicit and step-by-step for complex tasks
- Include relevant file names, function names, or error messages
- Reference what was previously done if continuing a task
- Claude Code retains full conversation history — you don't need to re-explain the whole project each time, just what's new
- Never re-paste the full GDD or project context on every call — Code already has it
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.
- 7d ago First seen · 102 lines · 1,006 tokens per session scan A 0ad09e273d49
claude-tmux-bridge CLAUDE.md is an instructions file published in the GitHub repository PiMPStudios/claude-tmux-bridge (0 stars, last pushed 4mo ago), licensed MIT. It adds 1,006 tokens to every session, about $0.0050 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-09-01.
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).
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).
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.
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.