tmux
Manage Persistent tmux Sessions
Long-running terminal tasks are hard to monitor across agent turns. This skill creates, lists, captures, controls, and cleans tmux sessions for persistent command execution.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "tmux" from https://skillstore.io/skills/dwsy-tmux.md and its manifest at https://skillstore.io/api/skills/dwsy-tmux/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "tmux". Start a background build and show how I can monitor it.
Expected outcome:
The skill creates a named tmux task session and returns the session identifier, attach command, and capture command for later monitoring.
Using "tmux". Check the latest output from my dev server session.
Expected outcome:
The skill captures recent pane text and summarizes whether the service appears ready, still starting, or failed.
Using "tmux". Clean old tmux sessions.
Expected outcome:
- Lists managed sessions with age and status.
- Removes sessions older than the requested threshold.
- Reports how many sessions were cleaned.
Security Audit
Medium RiskMost static findings are false positives from Markdown code fences, TypeScript template strings, documented installation paths, and benign shell redirection. The real risk is intentional local command execution through tmux session creation and key sending, plus temporary socket and session metadata storage.
Confirmed security concerns (1)
Capability review items (23)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (50)
📁 Filesystem access (50)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/dwsy-tmux/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dwsy-tmux?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dwsy-tmux?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dwsy-tmux/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dwsy-tmux.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Dwsy. (2026). tmux security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dwsy-tmux/audits/9BibTeX citation
@techreport{dwsy-dwsy-tmux-2026,
author = {Dwsy},
title = {tmux security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/dwsy-tmux/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "tmux security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "Dwsy"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/dwsy-tmux/audits/9"
identifiers:
- type: other
value: "skillstore:dwsy-tmux:audit:9"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Run long builds outside the main agent turn
Start a build or test command in tmux, then capture output later without losing process state.
Manage local development services
Launch a dev server in a named tmux session and inspect logs while other work continues.
Drive interactive terminal programs
Start a REPL or CLI, send input, and capture responses from the same persistent pane.
Try These Prompts
Use the tmux skill to start a task named build that runs my project build command. Show me how to capture the latest output.
Create a tmux service session for my development server, then check whether the server started successfully.
Start a Python REPL in tmux, send a simple expression, and capture the response from the pane.
List all tmux skill sessions, identify inactive sessions older than two days, and clean only those sessions.
Best Practices
- Review commands before creating sessions because they run in your local shell context.
- Use descriptive session names so cleanup and monitoring are clear.
- Capture output before killing a session if logs may be needed later.
Avoid
- Do not run untrusted commands or paste secrets into managed sessions.
- Do not leave long-lived services running without periodic cleanup.
- Do not assume tmux sessions isolate commands from your local filesystem.