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/devnullvoid/mcp-ssh-tmux/agents-mdgit clone --depth 1 https://github.com/devnullvoid/mcp-ssh-tmuxWhat 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.01489 | $0.01489 |
| Opus 5 | $0.00745 | $0.00745 |
| Sonnet 5 | $0.00298 | $0.00298 |
| Haiku 4.5 | $0.00149 | $0.00149 |
Grade A, and why
mcp-ssh-tmux 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 yesterday.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Continuity Guide
Source Reference
- Reference Project:
mcp-ssh-session - Absolute Path:
/home/jon/Dev/ai/mcp/mcp-ssh-session - Status: Pivot complete. Logic ported and improved.
Current Infrastructure
- Environment:
uv(Python 3.14+) - Command Runner:
just(seeJustfile) - Core Library:
libtmux(v0.30+ API used) - Logic:
mcp_ssh_tmux/session_manager.pyandserver.py.
Technical Insights for Future Agents
Philosophy: LLM-as-Observer
- The server provides raw visual snapshots. The AI agent is responsible for interpreting state (prompts, errors, etc.).
- Hints:
server.pyappends[INFO: ...]hints to snapshots when common shell prompts or password requests are detected.
Async Polling (Critical)
send_commandandread_fileMUST useawait asyncio.sleep(), nevertime.sleep(). The MCP server runs on an async event loop (FastMCP/uvicorn). Synchronous sleep blocks the entire event loop, making the server unresponsive to all other requests during the polling period. This was the root cause of a production bug wheresend_commandwith large timeouts (e.g., 60s fordocker service update) killed the server's ability to handle concurrentget_snapshotorlist_sessionscalls.
Key Dispatch
send_keys(literal mode) usespane.cmd("send-keys", *keys.split())to pass each token as a separate tmux argument. This lets tmux interpret key names (Enter,C-c,Tab) while still sending unrecognized tokens as literal text.- Do NOT use libtmux's
literal=True— it passes-lto tmux, which disables all key name interpretation (e.g.,"yes Enter"would type the word "Enter").
Connection Management
- SSH Execution: We start
sshdirectly as thewindow_shellcommand in tmux. This is more reliable than starting a shell and sending keys. - Config Resolution: We use
ssh -G <host>to resolve aliases and identity files from the user's~/.ssh/config. - Interactive Sessions: We intentionally avoid
BatchMode=yesfor the primary tmux-backed SSH session so the AI can handle interactive password/passphrase prompts visually. - Direct File Reads:
read_remote_filefirst attempts a separate non-interactivessh -o BatchMode=yes ... cat -- <path>using the resolved host/user/port/key info. If that fails, it falls back to bounded tmux history capture. - Persistence:
remain-on-exitis enabled viawindow.set_option("remain-on-exit", "on"). This allows capturing final errors after a connection dies.
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.
- yesterday First seen · 82 lines · 1,489 tokens per session scan A 1e23d419040e
mcp-ssh-tmux AGENTS.md is an instructions file published in the GitHub repository devnullvoid/mcp-ssh-tmux (6 stars, last pushed 2mo ago), licensed MIT. It adds 1,489 tokens to every session, about $0.0074 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-31.
Other instructions, from other repositories
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
openrouter-mcp-multimodal AGENTS.md
Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
seekstone CLAUDE.md
Instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
mcp-dockhand copilot-review.instructions.md
Instructions for strausmann/mcp-dockhand: When reviewing pull requests in this repository.
second-brain AGENTS.md
Instructions for LindaHaviv/second-brain, covering instructions for ai coding agents, what to read first, the rules (non-negotiable), common tasks, the sanctioned way and enforcement, not just instructions.