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 skills add ttttmr/pi-tmux-task --skill tmux-task-managergit clone --depth 1 https://github.com/ttttmr/pi-tmux-taskWrote 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/ttttmr/pi-tmux-task/tmux-task-manager)<a href="https://agentmods.dev/skills/ttttmr/pi-tmux-task/tmux-task-manager"><img src="https://agentmods.dev/badge/skills/ttttmr/pi-tmux-task/tmux-task-manager.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.00078 | $0.01639 |
| Opus 5 | $0.00039 | $0.00820 |
| Sonnet 5 | $0.00016 | $0.00328 |
| Haiku 4.5 | $0.00008 | $0.00164 |
Grade A, and why
tmux-task-manager 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pi Session Task Manager
Use this skill to start and observe background work for the current Pi conversation.
Golden path
Run the helper script bundled with this skill, with a stable task name and the command:
/path/to/this-skill/tmux-task-run.sh <task-name> -- '<command>'
Resolve tmux-task-run.sh relative to this SKILL.md and use that absolute path in bash commands. Do not rely on a PATH command and do not search the filesystem for another copy.
That is all. The helper automatically:
- reads the injected
$PI_TMUX_SESSION; - creates the tmux session if it does not exist;
- creates or reuses the named task window;
- runs the command from your current directory;
- keeps the window after exit so output can be inspected;
- lets Pi send a notification when the task exits, rings, disappears, or waits for input.
Record the helper output:
session=...
session_created=true|false
window_id=...
task=...
cwd=...
Error rule
Only handle this environment error yourself:
- If
$PI_TMUX_SESSIONis missing or empty, stop and report that the Pi task environment was not injected.
Do not preflight or repair tmux sessions. If $PI_TMUX_SESSION is set, call the helper and let it manage the session.
Do not:
- run
tmux lsto pick another session; - run
tmux has-sessionand then replace$PI_TMUX_SESSION; - invoke the helper as
PI_TMUX_SESSION=<guessed-session> tmux-task-run.sh ...; - copy a session name from another conversation.
If the helper itself fails, report the helper error instead of guessing a fix. If the helper script path from this skill is not available, report a Pi skill/package installation problem instead of locating another copy manually.
Missing session/window states
Treat tmux target errors as task state, not as a reason to guess or repair names:
| Observation | Meaning | Action |
|---|---|---|
$PI_TMUX_SESSION is empty |
Pi task environment was not injected | Stop and report the environment problem |
$PI_TMUX_SESSION is set, but tmux says can't find session: pi-... |
No task tmux session exists yet for this Pi conversation, or it was already cleaned up | This is normal when no background task is active. Start new background work with the helper; do not create/guess/repair the session yourself |
tmux says can't find window: @12 |
The recorded task window is gone, killed, or replaced | List current task windows once if orientation is needed; do not keep capturing the stale window_id |
tmux says can't find window: pi-... |
A session name was used where a window target was expected | Use tmux list-windows -t "$PI_TMUX_SESSION" for session-level listing, or tmux capture-pane -pt @12 for a recorded window |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 166 lines · 78 tokens per session scan A d37cfec84761
tmux-task-manager is a skill published in the GitHub repository ttttmr/pi-tmux-task (5 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 1,639 once invoked, about $0.0004 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 skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.