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/lftpadilla/agent-dev-kit/tmux-delegationnpx skills add LFTPadilla/agent-dev-kit --skill tmux-delegationgit clone --depth 1 https://github.com/LFTPadilla/agent-dev-kitWrote 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/lftpadilla/agent-dev-kit/tmux-delegation)<a href="https://agentmods.dev/skills/lftpadilla/agent-dev-kit/tmux-delegation"><img src="https://agentmods.dev/badge/skills/lftpadilla/agent-dev-kit/tmux-delegation.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.00058 | $0.02291 |
| Opus 5 | $0.00029 | $0.01145 |
| Sonnet 5 | $0.00012 | $0.00458 |
| Haiku 4.5 | $0.00006 | $0.00229 |
Grade A, and why
tmux-delegation 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 5d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Harness tmux Delegation
Manage and delegate tasks to coding agents running inside tmux panes and windows. Designed for orchestrators (like Hermes, OpenCode, Pi, or Tech Lead profiles) that decompose work and delegate execution to bounded workers across diverse CLI harnesses: Codex CLI, Claude Code, Pi CLI, OpenCode, cursor-agent, or standard shells.
The core rule: The orchestrator plans, routes, and audits; the worker implements in an isolated tmux pane.
1. Pane Selection & Allocation (Anti-Contamination Rule)
Never reuse a pane that has active context or conversation history from a different task or repository. Context pollution corrupts reasoning.
Inventory Existing Panes
# Check all windows and panes in the session with command, cwd, and alive status
tmux list-panes -t "$TMUX_SESSION" -F \
'#{window_index}:#{pane_index} #{pane_id} #{pane_current_command} #{pane_dead} #{pane_current_path}'
Pane Selection Matrix
| Pane Condition | Suitable? | Action |
|---|---|---|
| Target harness running, same repo, idle prompt | YES | Reset context if needed (/clear in Claude/Codex) and proceed. |
| Target harness running, different repo | NO | Open a new window. Do not contaminate active context. |
Empty shell (zsh/bash), same repo |
YES | Boot the desired agent directly in this pane. |
| Empty shell, different directory | YES | cd /abs/repo/path then launch agent. |
| All panes occupied or conflicting | NO | Spawn a fresh window. |
Spawning a Fresh Pane
When creating a new window, always specify the absolute working directory:
# 1. Create window with explicit cwd
tmux new-window -t "$TMUX_SESSION" -n "$TASK_SLUG" -c "$ABS_REPO_PATH"
# 2. Launch the target harness
# Claude Code:
tmux send-keys -t "$TMUX_SESSION:$WINDOW_INDEX" "claude --dangerously-skip-permissions" Enter
# Codex CLI:
tmux send-keys -t "$TMUX_SESSION:$WINDOW_INDEX" "codex" Enter
# Pi CLI:
tmux send-keys -t "$TMUX_SESSION:$WINDOW_INDEX" "pi" Enter
# OpenCode CLI:
tmux send-keys -t "$TMUX_SESSION:$WINDOW_INDEX" "opencode" Enter
# cursor-agent CLI:
tmux send-keys -t "$TMUX_SESSION:$WINDOW_INDEX" "cursor-agent" Enter
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.
- 5d ago First seen · 244 lines · 58 tokens per session scan A 93632dd76569
tmux-delegation is a skill published in the GitHub repository LFTPadilla/agent-dev-kit (2 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 2,291 once invoked, about $0.0003 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
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.