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.
git clone --depth 1 https://github.com/Aey-Sama/tmux-arsenalWrote 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/commands/aey-sama/tmux-arsenal/tmux-status)<a href="https://agentmods.dev/commands/aey-sama/tmux-arsenal/tmux-status"><img src="https://agentmods.dev/badge/commands/aey-sama/tmux-arsenal/tmux-status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/aey-sama/tmux-arsenal/tmux-status"><img src="https://agentmods.dev/badge/commands/aey-sama/tmux-arsenal/tmux-status.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.00296 |
| Opus 5.5 | $0.00006 | $0.00118 |
| Sonnet 5.5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
tmux-status 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 1mo 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.
What it actually says
Report the current tmux state. Run these and present the result as a compact table:
tmux list-sessions -F '#{session_name}|#{session_windows}w|attached=#{session_attached}|#{session_created}' 2>/dev/null || echo "no tmux server running"
tmux list-panes -a -F '#{session_name}|#{window_name}|#{pane_current_command}|dead=#{pane_dead}|exit=#{pane_dead_status}' 2>/dev/null
For each session show: name, window count, whether the user is attached, what is running, and any dead pane's real exit code.
Mark what this plugin created — _-prefixed sessions AND _-prefixed windows
inside the user's own sessions — versus the user's own.
End with how to reach each one. A window in a session the user is attached to needs no attach, only a jump:
tmux select-window -t <session>:<window> # they are already attached
tmux attach -t <name> # detached session
If a pane is dead with a non-zero #{pane_dead_status}, say so explicitly and
offer to show its output via tmux capture-pane -p -t <target>.
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.
- 1mo ago First seen · 28 lines · 16 tokens per session scan A 2cb7a1f94d75
tmux-status is a command published in the GitHub repository Aey-Sama/tmux-arsenal (1 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 296 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
cleanup
Remove statusline configuration before uninstalling the plugin.
setup
Interactive setup for Bash LSP development environment.
rot-swarm
Put the whole nine-lens roster on one subject simultaneously, one agent per lens on the Socio's model, and synthesise without flattening the disagreements.
rot-moe-install
Install the RoT MoE plugin from this clone -- verify the tree, arm the router, prove it is running. Never elevates, never downloads without asking.
rot-agent
Dispatch one lens of the RoT MoE roster as a living agent on a subject, and present its report inside its declared element.
status
Show game progress (no spoilers).