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 skills/jeremydev87/codingbuddy/tmux-masternpx skills add JeremyDev87/codingbuddy --skill tmux-mastergit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWrote 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/skills/jeremydev87/codingbuddy/tmux-master)<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/tmux-master"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/tmux-master.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.00040 | $0.04300 |
| Opus 5 | $0.00020 | $0.02150 |
| Sonnet 5 | $0.00008 | $0.00860 |
| Haiku 4.5 | $0.00004 | $0.00430 |
Grade A, and why
tmux-master 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 today.
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 — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tmux Master
Overview
tmux is the backbone of parallel AI agent execution. Misconfigured sessions cause orphaned processes, lost output, and silent failures that waste entire execution waves.
Core principle: Every tmux operation must be targeted to a specific session, window, or pane by ID — never rely on "current" context in automated workflows.
Violating the letter of this process is violating the spirit of reliable automation.
The Iron Law
ALWAYS USE EXPLICIT TARGETS (-t session:window.pane). NEVER ASSUME CONTEXT.
Automated workflows run outside interactive shells. tmux commands without -t targets silently operate on the wrong pane or fail entirely. There are no exceptions.
No exceptions:
- "The session is obvious" → Explicit
-tanyway - "There's only one pane" → Panes get added; target explicitly
- "I'll fix the target later" → Fix it now; debugging wrong-pane issues is expensive
When to Use
This skill provides background knowledge for ANY tmux operation:
- Creating sessions, windows, or panes for parallel agents
- Managing layouts for multi-pane orchestration
- Sending commands to panes programmatically
- Polling pane output for readiness or completion
- Styling panes for visual differentiation
- Debugging tmux-related failures in CI or automation
Relevant contexts:
- taskMaestro wave execution with multiple parallel panes
- AI agent orchestration requiring isolated terminal environments
- Any workflow that spawns, monitors, or communicates with tmux panes
When NOT to Use
- Interactive tmux usage — Manual terminal multiplexing needs no formal process
- Single-pane workflows — If you only need one terminal, tmux adds no value
- Docker/container orchestration — Use container tools, not tmux, for process isolation
Phase 1: Session, Window, and Pane Lifecycle
1.1 Session Management
# Create a named session (detached)
tmux new-session -d -s "my-session"
# Create session with a specific starting directory
tmux new-session -d -s "my-session" -c "/path/to/project"
# List all sessions
tmux list-sessions
# Kill a specific session
tmux kill-session -t "my-session"
# Kill ALL sessions (use with caution)
tmux kill-server
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.
- today First seen · 492 lines · 40 tokens per session scan A 94f30e05bb4e
tmux-master is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 4,300 once invoked, about $0.0002 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-03.
Other skills, from other repositories
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…
ring:checking-frontend-quality
Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for…
bzdesignprompt
为前端或网页设计任务选择并下载合适的 DESIGN.md 模板。当用户需要网页设计模板、UI 风格参考、设计系统、落地页或前端界面设计时,浏览长亭百智云 UI 设计模板库,根据产品场景和视觉偏好匹配模板,并将完整 DESIGN.md 保存到项目中。.
verify-quality
Verify code quality including naming conventions, organization, documentation, and general best practices. Use when asked to "verify quality", "check code quality", or "review code organization".